Systems and methods for electric vehicle charging

ABSTRACT

The present disclosure relates to a system and a method for electric vehicle charging. The system may perform the method to: receive a request for charging station recommendation from a client terminal; determine at least one charging station within a preset distance range of the client terminal; determine an evaluation for each of the at least one charging station based on one or more evaluation parameters; and transmitting, by the first computing device, the evaluation of the each of the at least one charging station and an identifier of the each of the at least one charging station to the client terminal.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of International Application No.PCT/CN2018/097382, filed on Jul. 27, 2018, which claims priority toChinese Patent Application No. 201711240909.4 filed on Nov. 30, 2017,and Chinese Patent Application No. 201711242974.0 filed on Nov. 30,2017, the contents of which are incorporated herein by reference intheir entirety.

TECHNICAL FIELD

The present disclosure generally relates to systems and methods foronline to offline services, and in particular, systems and methods forelectric vehicle charging.

BACKGROUND

With the popularity of new energy vehicles such as the electric cars orthe hybrid cars, more and more charging stations are provided to chargethe new energy vehicles. By distributing a wide range of charging piles,the driver of the new energy vehicle may locate a charging pile forcharging more efficiently, and the convenience of travel may beimproved. Meanwhile, the Internet-based online to offline services, suchas online taxi-calling services, have become increasingly popularbecause of their convenience. In addition to the traditional gasolinecars, the electric cars or the hybrid cars also become part of thetransportation means of the Internet-based online to offline services. Auser may obtain one or more charging stations using an applicationimplemented on a client terminal (e.g., a mobile phone). In general, aserver associated with the application may recommend the chargingstations based on information such as the number of charging piles of acharging station and/or user preference. Such information of a chargingstation may not be up-to-date, which causes a bad user experience.Further, to facilitate charging and payment, the user of the electriccar may need to communicate with the charging pile and a server viahis/her mobile phone. In the process of establishing communication, theuser may perform multiple association operations, such as initiating anassociation request, checking associating information, etc., which mayaffect the user experience. Therefore, it would be desirable to providesystems and methods to charge electric vehicles more efficiently.

SUMMARY

According to an aspect of the present disclosure, a method is provided.The method may be implemented on at least one device each of which hasat least one processor, a storage, and a communication platform toconnect to a network. The method may include one or more of thefollowing operations. The at least one processor may receive a requestfor charging station recommendation from a client terminal. The at leastone processor may determine at least one charging station within apreset distance range of the client terminal. The at least one processormay determine an evaluation for each of the at least one chargingstation based on one or more evaluation parameters. The one or moreevaluation parameters include at least one of: a price discount providedby the each of the at least one charging station, a distance between theeach of the at least one charging station and the client terminal, apreset recommendation value for the each of the at least one chargingstation, or a historical evaluation of the each of the at least onecharging station. The at least one processor may transmit the evaluationof the each of the at least one charging station and an identifier ofthe each of the at least one charging station to the client terminal.

In some embodiments, to determine an evaluation for each of the at leastone charging station, the at least one processor may obtain one or morepreset weight values corresponding to the one or more evaluationparameters, respectively. The at least one processor may estimate aweighted sum of the one or more evaluation parameters based on the oneor more preset weight values. The at least one processor may designatethe weighted sum of the one or more evaluation parameters as theevaluation of the each of the at least one charging station.

In some embodiments, the one or more preset weight values may include atleast one of: a first preset weight value corresponding to the pricediscount provided by the each of the at least one charging station being40%, a second preset weight value corresponding to the distance betweenthe each of the at least one charging station and the client terminalbeing 35%, a third preset weight value corresponding to the presetrecommendation value of the each of the at least one charging stationbeing 20%, or the fourth preset weight value corresponding to thehistorical evaluation value of the each of the at least one chargingstation being 5%.

In some embodiments, the at least one processor may further for each ofthe at least one charging station, determine the preset recommendationvalue based on one or more recommendation parameters. The one or morerecommendation parameters include at least one of: a number of chargingpiles at the each of the at least one charging station, a real-timeparking fee at the each of the at least one charging station, or a unitcharging price associated with the each of the at least one chargingstation.

In some embodiments, to determine the preset recommendation value, theat least one processor may obtain one or more preset percentagescorresponding to one of the one or more recommendation parameters,respectively. The at least one processor may determine the presetrecommendation value based on the one or more preset percentages,wherein the preset recommendation value is equal to a sum of the one ormore recommendation parameters multiplying the corresponding presetpercentage, respectively.

In some embodiments, the one or more preset percentages may include atleast one of: a first preset percentage corresponding to the number ofcharging piles at the each of the charging station being 45%, a secondpreset percentage corresponding to the real-time parking fee at the eachof the at least one charging station being 35%, or a third presetpercentage corresponding to the charging unit price associated with theeach of the at least one charging station being 20%.

In some embodiments, to transmit the evaluation of each of the at leastone charging station and an identifier of each of the at least onecharging station to the client terminal, the at least one processor maysorting the at least one charging station in a descending orderaccording to the evaluation of the at least one charging station. The atleast one processor may send the evaluation of each of the sorted atleast one charging station and the identifier of each of the sorted atleast one charging station to the client terminal for display.

In some embodiments, to transmit the evaluation of each of the at leastone charging station and an identifier of each of the at least onecharging station to the client terminal, the at least one processor maydetermine whether the evaluation of the each of the at least onecharging station is greater than or equal to a preset threshold. The atleast one processor may send the identifier of the each of the at leastone charging station to the client terminal for display in response to adetermination that the evaluation is greater than or equal to the presetthreshold.

In some embodiments, the at least one processor may further receive acharging request and an associating request for connecting the clientterminal and the second computing device from a target charging pile atone of the at least one charging station. The at least one processor maydetermine charging information for charging an electric vehicleassociated with the client terminal based on the charging request. Theat least one processor may establish a connection between the secondcomputing device and the client terminal based on the associatingrequest. The at least one processor may send the charging information tothe target charging pile for charging the electric vehicle based on thecharging information.

In some embodiments, the at least one processor may further obtain acurrent charging status of the electric vehicle from the target chargingpile. The at least one processor may send the current charging status tothe client terminal through the connection between the client terminaland the second computing device.

In some embodiments, the at least one processor may further determinewhether the charging for the electric vehicle is completed. The at leastone processor may determine a charging fee corresponding to the charginginformation in response to a determination that the charging for theelectric vehicle is completed. The at least one processor may send thecharging fee to the client terminal. The at least one processor maydeduct the charging fee from an electronic financial account associatedwith the client terminal upon receiving a payment confirmation for thecharging fee from the client terminal.

According to another aspect of the present disclosure, a method isprovided. The method may be implemented on at least one device each ofwhich has at least one processor, a storage, and a communicationplatform to connect to a network. The method may include one or more ofthe following operations. The at least one processor may receive acharging request and an associating request for connecting a clientterminal and the charging management device from a charging pile. The atleast one processor may determine charging information for charging anelectric vehicle associated with the client terminal based on thecharging request. The at least one processor may establish a connectionbetween the charging management device and the client terminal based onthe associating request. The at least one processor may send thecharging information to the charging pile for charging the electricvehicle based on the charging information.

In some embodiments, the at least one processor may further obtain acurrent charging status of the electric vehicle from the target chargingpile. The at least one processor may send the current charging status tothe client terminal through the connection between the client terminaland the charging management device.

In some embodiments, the at least one processor may further determinewhether the charging for the electric vehicle is completed. The at leastone processor may determine a charging fee corresponding to the charginginformation in response to a determination that the charging for theelectric vehicle is completed. The at least one processor may send thecharging fee to the client terminal. The at least one processor maydeduct the charging fee from an electronic financial account associatedwith the client terminal upon receiving a payment confirmation for thecharging fee from the client terminal.

According to another aspect of the present disclosure, a method isprovided. The method may be implemented on at least one device each ofwhich has at least one processor, a storage, and a communicationplatform to connect to a network. The method may include one or more ofthe following operations. The at least one processor may determinewhether the charging pile is connected with an electric vehicle. The atleast one processor may determine a client terminal associated with theelectric vehicle in response to a determination that the charging pileis connected with the electric vehicle. The at least one processor maysend a charging prompt and an associating prompt to the client terminal.The at least one processor may receive a charging request for chargingthe electric vehicle at the charging pile and an associating request forconnecting the client terminal with a charging management device fromthe client terminal. The at least one processor may send the chargingrequest and the associating request to the charging management devicevia the data exchange port.

In some embodiments, the at least one processor may further receive thecharging information from the charging management device. The at leastone processor may operate the charging pile to charge the electricvehicle based on the charging information.

In some embodiments, the at least one processor may further send currentcharging status of the electric vehicle to the charging managementdevice.

According to another aspect of the present disclosure, a method isprovided. The method may be implemented on at least one device each ofwhich has at least one processor, a storage, and a communicationplatform to connect to a network. The method may include one or more ofthe following operations. The at least one processor may receive acharging prompt and an associating prompt from a charging pile via thedata exchange port after the charging pile is connected to an electricvehicle associated with the client terminal. The at least one processormay cause a user interface of the client terminal to display thecharging prompt. The at least one processor may generate a chargingrequest for charging the electric vehicle based on a user interaction onthe user interface. The at least one processor may generate anassociating request for connecting the client terminal with a chargingmanagement device based on the associating prompt. The at least oneprocessor may send the charging request and the associating request tothe charging pile causing the charging pile to transfer the chargingrequest and the associating request to the charging management device.

In some embodiments, the at least one processor may further receive acurrent charging status of the electric vehicle sent by the chargingmanagement device. The at least one processor may display the currentcharging status on the user interface.

In some embodiments, the at least one processor may further receive astop charging request via the user interface.

In some embodiments, the at least one processor may further receive acharging fee sent by the charging management device. The at least oneprocessor may cause a display to display the charging fee on the userinterface. The at least one processor may obtain a payment confirmationfor the charging fee from the user interface. The at least one processormay send the payment confirmation to the charging management devicecausing the charging management device to deduct the charging fee froman electronic financial account associated with the client terminal.

According to another aspect of the present disclosure, a system isprovided. The system may include at least one storage media and at leastone processor configured to communicate with the at least one storagemedia. The at least one storage media may store a set of instructionsfor operating an online to offline service platform. When executing theset of instructions, the at least one processor may be directed toperform one or more of the following operations. The at least oneprocessor may receive a request for charging station recommendation froma client terminal. The at least one processor may determine at least onecharging station within a preset distance range of the client terminal.The at least one processor may determine an evaluation for each of theat least one charging station based on one or more evaluationparameters. The one or more evaluation parameters may include at leastone of: a price discount provided by the each of the at least onecharging station, a distance between the each of the at least onecharging station and the client terminal, a preset recommendation valuefor the each of the at least one charging station, or a historicalevaluation of the each of the at least one charging station. The atleast one processor may transmit the evaluation of the each of the atleast one charging station and an identifier of the each of the at leastone charging station to the client terminal.

According to another aspect of the present disclosure, a system isprovided. The system may include at least one storage media and at leastone processor configured to communicate with the at least one storagemedia. The at least one storage media may store a set of instructionsfor operating an online to offline service platform. When executing theset of instructions, the at least one processor may be directed toperform one or more of the following operations. The at least oneprocessor may receive a charging request and an associating request forconnecting a client terminal and a charging management device from acharging pile. The at least one processor may determine charginginformation for charging an electric vehicle associated with the clientterminal based on the charging request. The at least one processor mayestablish a connection between the charging management device and theclient terminal based on the associating request. The at least oneprocessor may send the charging information to the charging pile forcharging the electric vehicle based on the charging information.

According to another aspect of the present disclosure, a system isprovided. The system may include at least one storage media and at leastone processor configured to communicate with the at least one storagemedia. The at least one storage media may store a set of instructionsfor operating an online to offline service platform. When executing theset of instructions, the at least one processor may be directed toperform one or more of the following operations. The at least oneprocessor may determine whether the charging pile is connected with anelectric vehicle. The at least one processor may determine a clientterminal associated with the electric vehicle in response to adetermination that the charging pile is connected with the electricvehicle. The at least one processor may send a charging prompt and anassociating prompt to the client terminal. The at least one processormay receive a charging request for charging the electric vehicle at thecharging pile and an associating request for connecting the clientterminal with a charging management device from the client terminal. Theat least one processor may send the charging request and the associatingrequest to the charging management device via the data exchange port.

According to another aspect of the present disclosure, a system isprovided. The system may include at least one storage media and at leastone processor configured to communicate with the at least one storagemedia. The at least one storage media may store a set of instructionsfor operating an online to offline service platform. When executing theset of instructions, the at least one processor may be directed toperform one or more of the following operations. The at least oneprocessor may receive a charging prompt and an associating prompt from acharging pile via the data exchange port after the charging pile isconnected to an electric vehicle associated with the client terminal.The at least one processor may cause a user interface of the clientterminal to display the charging prompt. The at least one processor maygenerate a charging request for charging the electric vehicle based on auser interaction on the user interface. The at least one processor maygenerate an associating request for connecting the client terminal witha charging management device based on the associating prompt. The atleast one processor may send the charging request and the associatingrequest to the charging pile causing the charging pile to transfer thecharging request and the associating request to the charging managementdevice.

According to another aspect of the present disclosure, a non-transitorycomputer readable medium may comprise at least one set of instructionsfor providing an online to offline service. The at least one set ofinstructions may executed by at least one processor. The at least oneprocessor may receive a request for charging station recommendation froma client terminal. The at least one processor may determine at least onecharging station within a preset distance range of the client terminal.The at least one processor may determine an evaluation for each of theat least one charging station based on one or more evaluationparameters. The one or more evaluation parameters include at least oneof: a price discount provided by the each of the at least one chargingstation, a distance between the each of the at least one chargingstation and the client terminal, a preset recommendation value for theeach of the at least one charging station, or a historical evaluation ofthe each of the at least one charging station. The at least oneprocessor may transmit the evaluation of the each of the at least onecharging station and an identifier of the each of the at least onecharging station to the client terminal.

According to another aspect of the present disclosure, a non-transitorycomputer readable medium may comprise at least one set of instructionsfor providing an online to offline service. The at least one set ofinstructions may executed by at least one processor. The at least oneprocessor may receive a charging request and an associating request forconnecting a client terminal and a charging management device from acharging pile. The at least one processor may determine charginginformation for charging an electric vehicle associated with the clientterminal based on the charging request. The at least one processor mayestablish a connection between the charging management device and theclient terminal based on the associating request. The at least oneprocessor may send the charging information to the charging pile forcharging the electric vehicle based on the charging information.

According to another aspect of the present disclosure, a non-transitorycomputer readable medium may comprise at least one set of instructionsfor providing an online to offline service. The at least one set ofinstructions may executed by at least one processor. The at least oneprocessor may determine whether the charging pile is connected with anelectric vehicle. The at least one processor may determine a clientterminal associated with the electric vehicle in response to adetermination that the charging pile is connected with the electricvehicle. The at least one processor may send a charging prompt and anassociating prompt to the client terminal. The at least one processormay receive a charging request for charging the electric vehicle at thecharging pile and an associating request for connecting the clientterminal with a charging management device from the client terminal. Theat least one processor may send the charging request and the associatingrequest to the charging management device via the data exchange port.

According to another aspect of the present disclosure, a non-transitorycomputer readable medium may comprise at least one set of instructionsfor providing an online to offline service. The at least one set ofinstructions may executed by at least one processor. The at least oneprocessor may receive a charging prompt and an associating prompt from acharging pile via the data exchange port after the charging pile isconnected to an electric vehicle associated with the client terminal.The at least one processor may cause a user interface of the clientterminal to display the charging prompt. The at least one processor maygenerate a charging request for charging the electric vehicle based on auser interaction on the user interface. The at least one processor maygenerate an associating request for connecting the client terminal witha charging management device based on the associating prompt. The atleast one processor may send the charging request and the associatingrequest to the charging pile causing the charging pile to transfer thecharging request and the associating request to the charging managementdevice.

According to another aspect of the present disclosure, a system isprovided. The system may have at least one processor and storage. Thesystem may include a receiving unit configured to receive a request forcharging station recommendation from a client terminal. The system mayinclude a determining unit configured to determine at least one chargingstation within a preset distance range of the client terminal. Thesystem may include a calculating unit configured to determine anevaluation for each of the at least one charging station based on one ormore evaluation parameters. The one or more evaluation parametersinclude at least one of: a price discount provided by the each of the atleast one charging station, a distance between the each of the at leastone charging station and the client terminal, a preset recommendationvalue for the each of the at least one charging station, or a historicalevaluation of the each of the at least one charging station. The systemmay include a pushing unit configured to transmit the evaluation of theeach of the at least one charging station and an identifier of the eachof the at least one charging station to the client terminal.

According to another aspect of the present disclosure, a system isprovided. The system may have at least one processor and storage. Thesystem may include a receiving unit configured to receive a chargingrequest and an associating request for connecting a client terminal anda charging management device from a charging pile. The system mayinclude a determining unit configured to determine charging informationfor charging an electric vehicle associated with the client terminalbased on the charging request. The system may include a connecting unitconfigured to establish a connection between the charging managementdevice and the client terminal based on the associating request. Thesystem may include a sending unit configured to send the charginginformation to the charging pile for charging the electric vehicle basedon the charging information.

According to another aspect of the present disclosure, a system isprovided. The system may have at least one processor and storage. Thesystem may include a determining unit configured to determine whetherthe charging pile is connected with an electric vehicle, and determine aclient terminal associated with the electric vehicle in response to adetermination that the charging pile is connected with the electricvehicle. The system may include a sending unit configured to send acharging prompt and an associating prompt to the client terminal. Thesystem may include a receiving unit configured to receive a chargingrequest for charging the electric vehicle at the charging pile and anassociating request for connecting the client terminal with a chargingmanagement device from the client terminal. The system may include asending unit configured to send the charging request and the associatingrequest to the charging management device via the data exchange port.

According to another aspect of the present disclosure, a system isprovided. The system may have at least one processor and storage. Thesystem may include a receiving unit configured to receive a chargingprompt and an associating prompt from a charging pile via the dataexchange port after the charging pile is connected to an electricvehicle associated with the client terminal. The system may include adisplaying unit configured to cause a user interface of the clientterminal to display the charging prompt. The system may include agenerating unit configured to generate a charging request for chargingthe electric vehicle based on a user interaction on the user interface,and generate an associating request for connecting the client terminalwith a charging management device based on the associating prompt. Thesystem may include a sending unit configured to send the chargingrequest and the associating request to the charging pile causing thecharging pile to transfer the charging request and the associatingrequest to the charging management device.

Additional features will be set forth in part in the description whichfollows, and in part will become apparent to those skilled in the artupon examination of the following and the accompanying drawings or maybe learned by production or operation of the examples. The features ofthe present disclosure may be realized and attained by practice or useof various aspects of the methodologies, instrumentalities, andcombinations set forth in the detailed examples discussed below.

BRIEF DESCRIPTION OF THE DRAWINGS

The present disclosure is further described in terms of exemplaryembodiments. These exemplary embodiments are described in detail withreference to the drawings. These embodiments are non-limiting exemplaryembodiments, in which like reference numerals represent similarstructures throughout the several views of the drawings, and wherein:

FIG. 1 is a schematic diagram of an exemplary online to offline servicesystem according to some embodiments of the present disclosure;

FIG. 2 is a block diagram of an exemplary mobile device configured toimplement a specific system disclosed in the present disclosure;

FIG. 3 is a block diagram illustrating an exemplary computing deviceaccording to some embodiments of the present disclosure;

FIG. 4 is a block diagram illustrating an exemplary server according tosome embodiments of the present disclosure;

FIG. 5 is a flowchart illustrating an exemplary process 500 for chargingan electric vehicle according to some embodiments of the presentdisclosure;

FIG. 6 is a block diagram illustrating an exemplary charging stationrecommendation device according to some embodiments of the presentdisclosure;

FIG. 7 is a flowchart illustrating an exemplary process for chargingstation recommendation according to some embodiments of the presentdisclosure;

FIG. 8 is a block diagram illustrating an exemplary charging managementdevice 420 according to some embodiments of the present disclosure;

FIG. 9 is a flowchart illustrating an exemplary process for operating acharging pile to charge an electric vehicle according to someembodiments of the present disclosure;

FIG. 10 is a block diagram illustrating an exemplary processor of acharging pile according to some embodiments of the present disclosure.

FIG. 11 is a flowchart illustrating an exemplary process for charging anelectric vehicle according to some embodiments of the presentdisclosure;

FIG. 12 is a block diagram illustrating an exemplary processor of clientterminal according to some embodiments of the present disclosure;

FIG. 13 is a flowchart illustrating an exemplary process for charging anelectric vehicle according to some embodiments of the presentdisclosure;

FIG. 14 is a flowchart illustrating an exemplary process for charging anelectric vehicle according to some embodiments of the presentdisclosure;

FIG. 15 is a flowchart illustrating an exemplary process for charging anelectric vehicle according to some embodiments of the presentdisclosure; and

FIG. 16 shows a schematic diagram illustrating a charging processaccording to some embodiments of the present disclosure.

DETAIL DESCRIPTION

The following description is presented to enable any person skilled inthe art to make and use the present disclosure, and is provided in thecontext of a particular application and its requirements. Variousmodifications to the disclosed embodiments will be readily apparent tothose skilled in the art, and the general principles defined herein maybe applied to other embodiments and applications without departing fromthe spirit and scope of the present disclosure. Thus, the presentdisclosure is not limited to the embodiments shown, but is to beaccorded the widest scope consistent with the claims.

The terminology used herein is for the purpose of describing particularexample embodiments only and is not intended to be limiting. As usedherein, the singular forms “a,” “an,” and “the” may be intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprise,”“comprises,” and/or “comprising,” “include,” “includes,” and/or“including,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

These and other features, and characteristics of the present disclosure,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, may become more apparent upon consideration of thefollowing description with reference to the accompanying drawings, allof which form a part of this disclosure. It is to be expresslyunderstood, however, that the drawings are for the purpose ofillustration and description only and are not intended to limit thescope of the present disclosure. It is understood that the drawings arenot to scale.

The flowcharts used in the present disclosure illustrate operations thatsystems implement according to some embodiments in the presentdisclosure. It is to be expressly understood, the operations of theflowchart may be implemented not in order. Conversely, the operationsmay be implemented in inverted order, or simultaneously. Moreover, oneor more other operations may be added to the flowcharts. One or moreoperations may be removed from the flowcharts.

Moreover, while the system and method in the present disclosure isdescribed primarily in regard to process a query, it should also beunderstood that this is only one exemplary embodiment. The system ormethod of the present disclosure may be applied to any other kind ofsearch service. For example, the system or method of the presentdisclosure may be applied to transportation systems of differentenvironments including land, ocean, aerospace, or the like, or anycombination thereof. The vehicle of the transportation systems mayinclude a taxi, a private car, a hitch, a bus, a train, a bullet train,a high speed rail, a subway, a vessel, an aircraft, a spaceship, ahot-air balloon, a driverless vehicle, or the like, or any combinationthereof. The transportation system may also include any transportationsystem for management and/or distribution, for example, a system forsending and/or receiving an express. The application of the system ormethod of the present disclosure may include a webpage, a plug-in of abrowser, a client terminal, a custom system, an internal analysissystem, an artificial intelligence robot, or the like, or anycombination thereof.

The term “passenger,” “requester,” “service requester,” and “customer”in the present disclosure are used interchangeably to refer to anindividual, an entity that may request or order a service. Also, theterm “driver,” “provider,” “service provider,” and “supplier” in thepresent disclosure are used interchangeably to refer to an individual,entity or a tool that may provide a service or facilitate the providingof the service. The term “user” in the present disclosure may refer toan individual, an entity that may request a service, order a service,provide a service, or facilitate the providing of the service. Forexample, the user may be a passenger, a driver, an operator, or thelike, or any combination thereof. In the present disclosure,“passenger,” “user equipment,” “client terminal,” and “passengerterminal” may be used interchangeably, and “driver” and “driverterminal” may be used interchangeably.

The term “service request” refers to a request that may be initiated bya user (e.g., a passenger, a requester, an operator, a servicerequester, a customer, a driver, a provider, a service provider, asupplier). For example, the service request may relate to a chargingstation recommendation. As another example, the service request mayrelate to charge an electric vehicle using a charging pile.

The system may find applications in many fields, e.g., a taxitransportation service, a driving application, a distributingapplication, a map application, or a navigation application, etc.

An aspect of the present disclosure relates to systems and methods foronline to offline service. The system may receive a request for chargingstation recommendation from a client terminal. The system may determineat least one charging station within a preset distance range of theclient terminal. The system may evaluate each of the at least onecharging station based on one or more evaluation parameters. The one ormore evaluation parameters include at least one of a price discountprovided by the each of the at least one charging station, a distancebetween the each of the at least one charging station and the clientterminal, a preset recommendation value for the each of the at least onecharging station, or a historical evaluation of the each of the at leastone charging station. The system may transmit the evaluation of the eachof the at least one charging station and an identifier of the each ofthe at least one charging station to the client terminal.

FIG. 1 is a block diagram of an exemplary online to offline servicesystem 100 according to some embodiments of the present disclosure. Forexample, the online to offline service system 100 may be an onlinetransportation service platform for transportation service such as taxihailing, chauffeur service, express car, carpool, bus service, driverhire and shuttle service. Further, the online transportation serviceplatform may include a charging service platform for electric vehicles,such as electric cars, electric motorcycles, electric bicycle, etc. Theonline to offline service system 100 may include a server 110, a network120, one or more client terminals 130, one or more electric vehicles140, storage 150, and one or more charging stations 160. It should benoted that the online to offline service system 100 shown in FIG. 1 ismerely an example, and not intended to be limiting.

In some embodiments, the server 110 may be a single server, or a servergroup. The server group may be centralized, or distributed (e.g., server110 may be a distributed system). In some embodiments, the server 110may be local or remote. For example, the server 110 may accessinformation and/or data stored in the one or more client terminals 130,and/or the storage 150 via the network 120. As another example, theserver 110 may be directly connected to the one or more client terminals130, the storage 150, and/or one or more charging stations 160 to accessstored information and/or data. In some embodiments, the server 110 maybe implemented on a cloud platform. Merely by way of example, the cloudplatform may include a private cloud, a public cloud, a hybrid cloud, acommunity cloud, a distributed cloud, an inter-cloud, a multi-cloud, orthe like, or any combination thereof. In some embodiments, the server110 may be implemented on a computing device 300 having one or morecomponents illustrated in FIG. 3 in the present disclosure.

In some embodiments, the server 110 may include one or more processingdevices 112. The processing device 112 may process information and/ordata relating to charging station recommendation and/or chargingmanagement to perform one or more functions described in the presentdisclosure. For example, the processing device 112 may receive a requestfor charging station recommendation from the client terminal 130. Theprocessing device 112 may determine one or more charging stations basedon the request for charging station recommendation and transmit thedetermined one or more charging stations to the client terminal 130. Asanother example, the processing device 112 may receivie a request forcharging an electric vehicle (e.g.,an electric car 140-1) from acharging pile at the charging station 160. The processing device 112 maycontrol the charging pile to charge the electric vehicle. Moredescriptions for the processing device 112 may be found elsewhere in thepresent disclosure (e.g., FIG. 4, and the descriptions thereof).

In some embodiments, the processing device 112 may include one or moreprocessing engines (e.g., signal-core processing engine(s) or multi-coreprocessor(s)). Merely by way of example, the processing device 112 mayinclude a central processing unit (CPU), an application-specificintegrated circuit (ASIC), an application-specific instruction-setprocessor (ASIP), a graphics processing unit (GPU), a physics processingunit (PPU), a digital signal processor (DSP), a field-programmable gatearray (FPGA), a programmable logic device (PLD), a controller, amicrocontroller unit, a reduced instruction-set computer (RISC), amicroprocessor, or the like, or any combination thereof.

The network 120 may facilitate exchange of information and/or data. Insome embodiments, one or more components in the online to offlineservice system 100 (e.g., the server 110, the one or more clientterminals 130, or the storage 150) may send information and/data toother component(s) in the online to offline service system 100 via thenetwork 120. For example, the server 110 may obtain/acquire servicerequest from the client terminal 130 via the network 120. In someembodiments, the network 120 may be any type of wired or wirelessnetwork, or any combination thereof. Merely by way of example, thenetwork 120 may include a cable network, a wireline network, an opticalfiber network, a telecommunications network, an intranet, an internet, alocal area network (LAN), a wide area network (WAN), a wireless localarea network (WLAN), a metropolitan area network (MAN), a wide areanetwork (WAN), a public telephone switched network (PTSN), a Bluetoothnetwork, a ZigBee network, a near field communication (NFC) network, orthe like, or any combination thereof. In some embodiments, the network120 may include one or more network access points. For example, thenetwork 120 may include wired or wireless network access points such asbase stations and/or internet exchange points 120-1, 120-2, . . . ,through which one or more components of the online to offline servicesystem 100 may be connected to the network 120 to exchange data and/orinformation.

In some embodiments, the client terminal 130 may include a mobile device130-1, a tablet computer 130-2, a laptop computer 130-3, a built-indevice in a motor vehicle 130-4, or the like, or any combinationthereof. In some embodiments, the client terminal 130 may facilitate acommunication and/or interaction between the processing device 112 and auser associated with the client terminal 130. For example, the clientterminal 130 may generate a request for charging station recommendationbased on an input entered by the user via a user interface. Theprocessing device 112 may receive the request for charging stationrecommendation from the client terminal 130. As another example, theprocessing device 112 may transmit one or more charging stations to theclient terminal 130 to be displayed for the user.

In some embodiments, the client terminal 130 may be connected to and/orcommunicate with a charging pile at the charging station 160. Forexample, the client terminal 130 may receive a charging prompt and anassociating prompt from the charging pile via a data exchange portimplemented on the client terminal 130 after the charging pile isconnected to an electric vehicle. The client terminal 130 may generate acharging request for charging the electric vehicle based on the chargingprompt according to a user interaction inputted by the user via the userinterface. The client terminal 130 may generate an associating requestfor connecting the client terminal with a charging management devicebased on the associating prompt. The client terminal 130 may send thecharging request and the associating request to the charging pilecausing the charging pile to transfer the charging request and theassociating request to the processing device 112.

In some embodiments, the mobile device 130-1 may include a smart homedevice, a wearable device, a smart mobile device, a virtual realitydevice, an augmented reality device, or the like, or any combinationthereof. In some embodiments, the smart home device may include a smartlighting device, a control device of an intelligent electricalapparatus, a smart monitoring device, a smart television, a smart videocamera, an interphone, or the like, or combination thereof. In someembodiments, the wearable device may include a smart bracelet, a smartfootgear, a smart glass, a smart helmet, a smart watch, a smartclothing, a smart backpack, a smart accessory, or the like, or anycombination thereof. In some embodiments, the smart mobile device mayinclude a smartphone, a personal digital assistance (PDA), a gamingdevice, a navigation device, a point of sale (POS) device, or the like,or any combination. In some embodiments, the virtual reality deviceand/or the augmented reality device may include a virtual realityhelmet, a virtual reality glass, a virtual reality patch, an augmentedreality helmet, an augmented reality glass, an augmented reality patch,or the like, or any combination thereof. For example, the virtualreality device and/or the augmented reality device may include a GoogleGlass, an Oculus Rift, a Hololens, a Gear VR, etc. In some embodiments,built-in device in the motor vehicle 130-4 may include an onboardcomputer, an onboard television, etc. In some embodiments, the clientterminal 130 may be a device with positioning technology for locatingthe position of the service requester and/or the client terminal 130.

The one or more electric vehicles 140 may include one or more electriccars (e.g., an electric car 140-1, an electric car 140-2, etc.), one ormore electric motors 140-3, one or more electric bikes 140-4, or thelike, or the combination thereof. The electric vehicle 140 may includean identifier configured to distinguish with other electric vehicles.The identifier of the electric vehicle 140 may include vehicleinformation such as vehicle type, vehicle brand, vehicle license,vehicle number, or the like, or a combination thereof. The informationrelating to the client terminal 130 may include identificationinformation associated with the client terminal 130 (e.g., the MACaddress of a mobile phone), an electronic bank account associated withthe client terminal 130, or the like, or a combination thereof.

The storage 150 may store data and/or instructions. In some embodiments,the storage 150 may store data obtained from the one or more clientterminals. For example, the storage 150 may store a request for chargingstation recommendation and/or charging an electric vehicle from theclient terminal 130. As another example, the storage 150 may store thevehicle information relating to the electric vehicle 140. In someembodiments, the storage 150 may store data and/or instructions that theserver 110 may execute or use to perform exemplary methods described inthe present disclosure. In some embodiments, the storage 150 may includea mass storage, a removable storage, a volatile read-and-write memory, aread-only memory (ROM), or the like, or any combination thereof.Exemplary mass storage may include a magnetic disk, an optical disk, asolid-state drives, etc. Exemplary removable storage may include a flashdrive, a floppy disk, an optical disk, a memory card, a zip disk, amagnetic tape, etc. Exemplary volatile read-and-write memory may includea random access memory (RAM). Exemplary RAM may include a dynamic RAM(DRAM), a double date rate synchronous dynamic RAM (DDR SDRAM), a staticRAM (SRAM), a thyristor RAM (T-RAM), and a zero-capacitor RAM (Z-RAM),etc. Exemplary ROM may include a mask ROM (MROM), a programmable ROM(PROM), an erasable programmable ROM (EPROM), an electrically-erasableprogrammable ROM (EEPROM), a compact disk ROM (CD-ROM), and a digitalversatile disk ROM, etc. In some embodiments, the storage 150 may beimplemented on a cloud platform. Merely by way of example, the cloudplatform may include a private cloud, a public cloud, a hybrid cloud, acommunity cloud, a distributed cloud, an inter-cloud, a multi-cloud, orthe like, or any combination thereof.

In some embodiments, the storage 150 may be connected to the network 120to communicate with one or more components in the online to offlineservice system 100 (e.g., the server 110, the one or more clientterminals, etc.). One or more components in the online to offlineservice system 100 may access the data and/or instructions stored in thestorage 150 via the network 120. In some embodiments, the storage 150may be directly connected to or communicate with one or more componentsin the online to offline service system 100 (e.g., the server 110, theone or more client terminals, etc.). In some embodiments, the storage150 may be part of the server 110.

In some embodiments, one or more components in the online to offlineservice system 100 (e.g., the server 110, the one or more clientterminals, etc.) may have a permission to access the storage 150. Insome embodiments, one or more components in the online to offlineservice system 100 may read and/or modify information relating to theclient terminal 130 when one or more conditions are met. For example,the server 110 may read and/or modify one or more users' informationafter a service (for example, charging service.

In some embodiments, information exchanging of one or more components ofthe online to offline service system 100 may be achieved by way ofrequesting a search service. The object of the search service requestmay be any product. In some embodiments, the product may be a tangibleproduct or an immaterial product. The tangible product may include food,medicine, commodity, chemical product, electrical appliance, clothing,car, housing, luxury, or the like, or any combination thereof. Theimmaterial product may include a servicing product, a financial product,a knowledge product, an internet product, or the like, or anycombination thereof. The internet product may product may include anindividual host product, a web product, a mobile internet product, acommercial host product, an embedded product, or the like, or anycombination thereof. The mobile internet product may be used in asoftware of a mobile terminal, a program, a system, or the like, or anycombination thereof. The mobile terminal may include a tablet computer,a laptop computer, a mobile phone, a personal digital assistance (PDA),a smart watch, a point of sale (POS) device, an onboard computer, anonboard television, a wearable device, or the like, or any combinationthereof. For example, the product may be any software and/or applicationused on the computer or mobile phone. The software and/or applicationmay relate to socializing, shopping, transporting, entertainment,learning, investment, or the like, or any combination thereof. In someembodiments, the software and/or application relating to transportingmay include a traveling software and/or application, a vehiclescheduling software and/or application, a mapping software and/orapplication, etc. In the vehicle scheduling software and/or application,the vehicle may include a horse, a carriage, a rickshaw (e.g., awheelbarrow, a bike, a tricycle, etc.), a car (e.g., a taxi, a bus, aprivate car, etc.), a train, a subway, a vessel, an aircraft (e.g., anairplane, a helicopter, a space shuttle, a rocket, a hot-air balloon,etc.), or the like, or any combination thereof.

The charging station 160 may include one or more charging pilesconfigured to charge an electric vehicle (e.g., the electric vehicle140). In some embodiments, a charging pile may have at least oneprocessor, at least one storage device, and a data exchange portcommunicatively connected to the network 120. In some embodiments, thecharging pile (e.g., the at least one processor) may determine whetherthe charging pile is connected with an electric vehicle. The chargingpile may determine a client terminal associated with the electricvehicle in response to a determination that the charging pile isconnected with the electric vehicle. The charging pile may send acharging prompt and an associating prompt to the client terminal. Thecharging pile may receive a charging request for charging the electricvehicle at the charging pile and an associating request for connectingthe client terminal with a charging management device (e.g., theprocessing device 112) from the client terminal. The charging pile maysend the charging request and the associating request to the chargingmanagement device (e.g., the processing device 112) via the dataexchange port. In some embodiments, the charging pile may receive, bythe at least one processor charging information from the chargingmanagement device (e.g., the processing device 112) and operate, by theat least one processor, the charging pile to charge the electric vehiclebased on the charging information. The charging information may includeone or more charging parameters, for example, charging volume, chargingpercentage, charging duration, etc.

One of ordinary skill in the art would understand that when an elementof the online to offline service system 100 performs, the element mayperform through electrical signals and/or electromagnetic signals. Forexample, when the client terminal 130 processes a task, such as making adetermination, identifying or selecting an object, the client terminal130 may operate logic circuits in its processor to process such task.When the client terminal 130 sends a request (e.g., a charging request,a request for charging station recommendation, etc.) to the server 110,a processor of the client terminal 130 may generate electrical signalsencoding the request. The processor of the client terminal 130 may thensend the electrical signals to an output port. If the client terminal130 communicates with the server 110 via a wired network, the outputport may be physically connected to a cable, which further transmit theelectrical signal to an input port of the server 110. If the clientterminal 130 communicates with the server 110 via a wireless network,the output port of the client terminal 130 may be one or more antennas,which convert the electrical signal to electromagnetic signal.Similarly, a client terminal 130 may process a task through operation oflogic circuits in its processor, and receive an instruction and/orservice request from the server 110 via electrical signal orelectromagnet signals. Within an electronic device, such as the clientterminal 130, a charging pile 160, and/or the server 110, when aprocessor thereof processes an instruction, sends out an instruction,and/or performs an action, the instruction and/or action is conductedvia electrical signals. For example, when the processor retrieves orsaves data from a storage medium, it may send out electrical signals toa read/write device of the storage medium, which may read or writestructured data in the storage medium. The structured data may betransmitted to the processor in the form of electrical signals via a busof the electronic device. Here, an electrical signal may refer to oneelectrical signal, a series of electrical signals, and/or a plurality ofdiscrete electrical signals.

FIG. 2 is a block diagram of an exemplary mobile device configured toimplement a specific system disclosed in the present disclosure. In someembodiments, a client terminal device configured to display andcommunicate information related to locations may be a mobile device 200.The mobile device may include but is not limited to a smartphone, atablet computer, a music player, a portable game console, a GPSreceiver, a wearable calculating device (e.g. glasses, watches, etc.),or the like. The mobile device 200 may include one or more centralprocessing units (CPUs) 240, one or more graphical processing units(GPUs) 230, a display 220, a memory 260, a communication unit 210, astorage unit 290, and one or more input/output (I/O) devices 250.Moreover, the mobile device 200 may also be any other suitable componentthat includes but is not limited to a system bus or a controller (notshown in FIG. 2). As shown in FIG. 2, a mobile operating system 270(e.g. 10S, Android, Windows Phone, etc.) and one or more applications280 may be loaded from the storage unit 290 to the memory 260 andimplemented by the CPUs 240. The application 280 may include a browseror other mobile applications configured to receive and processinformation related to a query (e.g., a name of a location) inputted bya user in the mobile device 200. The user may obtain information relatedto one or more search results through the system I/O device 250, andprovide the information to the server 110 and/or other modules or unitsof the online to offline service system 100 (e.g., the network 120).

In order to implement various modules, units and their functionsdescribed above, a computer hardware platform may be used as hardwareplatforms of one or more elements (e.g., the server 110 and/or othersections of the online to offline service system 100 described in FIG. 1through FIG. 16). Since these hardware elements, operating systems andprogram languages are common, it may be assumed that persons skilled inthe art may be familiar with these techniques and they may be able toprovide information required in the online to offline service accordingto the techniques described in the present disclosure. A computer withuser interface may be used as a personal computer (PC), or other typesof workstations or terminal devices. After being properly programmed, acomputer with user interface may be used as a server. It may beconsidered that those skilled in the art may also be familiar with suchstructures, programs, or general operations of this type of computerdevice. Thus, extra explanations are not described for the Figures.

FIG. 3 is a block diagram illustrating exemplary hardware and softwarecomponents of a computing device 300 on which the server 110, the clientterminal 130, and the charging station 160 may be implemented accordingto some embodiments of the present disclosure. The computing device 300may be configured to perform one or more functions of the server 110,the client terminal 130, and the charging station 160 disclosed in thisdisclosure. For example, the processing device 112 may be implemented onthe computing device 300 and configured to perform functions of theprocessing device 112 disclosed in this disclosure.

The computing device 300 may be a general-purpose computer or a specialpurpose computer, both may be used to implement an online to offlineservice system 100 for the present disclosure. The computing device 300may be used to implement any component of the online to offline servicesystem 100 as described herein. For example, the processing device 112may be implemented on the computing device 300, via its hardware,software program, firmware, or a combination thereof. Although only onesuch computer is shown, for convenience, the computer functions relatingto the search service as described herein may be implemented in adistributed fashion on a number of similar platforms to distribute theprocessing load.

The computing device 300, for example, may include COM ports 250connected to and from a network connected thereto to facilitate datacommunications. The computing device 300 may also include a processor320, in the form of one or more processors, for executing programinstructions. The exemplary computer platform may include an internalcommunication bus 310, program storage and data storage of differentforms, for example, a disk 370, and a read only memory (ROM) 330, or arandom access memory (RAM) 340, for various data files to be processedand/or transmitted by the computer. The exemplary computer platform mayalso include program instructions stored in the ROM 330, RAM 340, and/orother type of non-transitory storage medium to be executed by theprocessor 320. The methods and/or processes of the present disclosuremay be implemented as the program instructions. The computing device 300may also include an I/O component 360, supporting input/output betweenthe computer and other components therein. The computing device 300 mayalso receive programming and data via network communications.

The computing device 300 may also include a hard disk controllercommunicated with a hard disk, a keypad/keyboard controller communicatedwith a keypad/keyboard, a serial interface controller communicated witha serial peripheral equipment, a parallel interface controllercommunicated with a parallel peripheral equipment, a display controllercommunicated with a display, or the like, or any combination thereof.

Merely for illustration, only one CPU and/or processor is described inthe computing device 300. However, it should be noted that the computingdevice 300 in the present disclosure may also include multiple CPUsand/or processors, thus operations and/or method steps that areperformed by one CPU and/or processor as described in the presentdisclosure may also be jointly or separately performed by the multipleCPUs and/or processors. For example, if in the present disclosure theCPU and/or processor of the computing device 300 executes both operationA and operation B, it should be understood that operation A andoperation B may also be performed by two different CPUs and/orprocessors jointly or separately in the computing device 300 (e.g., thefirst processor executes operation A and the second processor executesoperation B, or the first and second processors jointly executeoperations A and B).

FIG. 4 is a block diagram illustrating an exemplary server 110 accordingto some embodiments of the present disclosure. The server 110 mayinclude one or more processing devices, such as a charging stationrecommendation device 410 and a charging management device 420.

The charging station recommendation device 410 may be configured to pushat least one charging station to the client terminal 130. For example,the charging station recommendation device 410 may receive a request forcharging station recommendation from a client terminal. The chargingstation recommendation device 410 may determine at least one chargingstation within a preset distance range of the client terminal 130 andevaluate each of the at least one charging station based on one or moreevaluation parameters. The one or more evaluation parameters may includeat least one of: a price discount provided by the each of the at leastone charging station, a distance between the each of the at least onecharging station and the client terminal, a preset recommendation valuefor the each of the at least one charging station, or a historicalevaluation of the each of the at least one charging station. Thecharging station recommendation device 410 may transmit the evaluationof the each of the at least one charging station and an identifier ofthe each of the at least one charging station to the client terminal130. For example, the charging station recommendation device 410 maysort the at least one charging station in a descending order accordingto the evaluation of the at least one charging station. The chargingstation recommendation device 410 may send the evaluation of each of thesorted at least one charging station and the identifier of each of thesorted at least one charging station to the client terminal for display.As another example, the charging station recommendation device 410 maydetermine whether the evaluation of the each of the at least onecharging station is greater than or equal to a preset threshold. Thecharging station recommendation device 410 may send the identifier ofthe each of the at least one charging station to the client terminal fordisplay in response to a determination that the evaluation is greaterthan or equal to the preset threshold.

The charging management device 420 may be configured to charging controlof the electric vehicle 140. For example, the charging management device420 may receive a charging request and an associating request forconnecting a client terminal and the charging management device from acharging pile. The charging management device 420 may determine charginginformation for charging an electric vehicle associated with the clientterminal based on the charging request. The charging management device420 may establish a connection between the charging management deviceand the client terminal based on the associating request. The chargingmanagement device 420 may send the charging information to the chargingpile for charging the electric vehicle based on the charginginformation.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example, thecharging station recommendation device 410 and the charging managementdevice 420 may be implemented by two separate severs.

FIG. 5 is a flowchart illustrating an exemplary process 500 for chargingan electric vehicle according to some embodiments of the presentdisclosure. The process 500 may be executed by the online to offlineservice system 100. For example, the process 500 may be implemented as aset of instructions (e.g., an application) stored in the storage device150. The processing device 112 may execute the set of instructions and,when executing the instructions, it may be configured to perform theprocess 500. The operations of the illustrated process presented beloware intended to be illustrative. In some embodiments, the process 500may be accomplished with one or more additional operations not describedand/or without one or more of the operations discussed. Additionally,the order in which the operations of the process as illustrated in FIG.5 and described below is not intended to be limiting.

In 510, the processing device 112 (e.g., the charging stationrecommendation device 410) may receive a request for charging stationrecommendation from a client terminal (e.g., the client terminal 130).In some embodiments, the request for charging station recommendation maybe generated by the client terminal based on an input entered by a uservia a user interface (e.g., an application) of the client terminal. Theclient terminal may send the charging request to the processing device112 via the network 120.

In 520, the processing device 112 (e.g., the charging stationrecommendation device 410) may transmit information related to at leastone charging station to the client terminal. The information related toat least one charging station to the client terminal may include anevaluation of the at least one charging station, an identifier of the atleast one charging station, an address of the at least one chargingstation, etc. The processing device 112 (e.g., the charging stationrecommendation device 410) may determine at least one charging stationwithin a preset distance range of the client terminal in response to therequest for charging station recommendation. In some embodiments, theprocessing device 112 (e.g., the charging station recommendation device410) may transmit information related to the at least one chargingstation to the client terminal. In some embodiments, the processingdevice 112 (e.g., the charging station recommendation device 410) mayevaluate each of the at least one charging station based on one or moreevaluation parameters. The one or more evaluation parameters may includea price discount provided by the each of the at least one chargingstation, a distance between the each of the at least one chargingstation and the client terminal, a preset recommendation value for theeach of the at least one charging station, a historical evaluation ofthe each of the at least one charging station, or the like, or acombination thereof. The processing device 112 (e.g., the chargingstation recommendation device 410) may transmit the evaluation of theeach of the at least one charging station and an identifier of the eachof the at least one charging station to the client terminal. Moredescriptions for transmitting at least one charging station to theclient terminal 130 may be found elsewhere in the present disclosure(e.g., FIG. 7 and the descriptions thereof).

In 530, the processing device 112 (e.g., the charging management device420) may receive a charging request for charging an electric vehiclefrom a charging pile at a target charging station of the at least onecharging station. In some embodiments, the target charging station maybe selected by the user manually from the at least one charging stationdetermined in 520. In some embodiments, the target charging station maybe automatically determined by the processing device 112. For example,the processing device 112 may determine a charging station nearest fromthe user or the client terminal as the target charging station. Asanother example, the processing device 112 may determine a chargingstation with the highest evaluation as the target charging station.

The charging request may include vehicle information relating to theelectric vehicle to be charged. The vehicle information relating to theelectric vehicle may include the license number of the electric vehicle,the type of the electric vehicle, the current dump energy of theelectric vehicle, the type of a charger for the electric vehicle, etc.In some embodiments, the charging request may be generated by thecharging pile when the electric vehicle is connected to the chargingpile. The processing device 112 (e.g., the charging management device420) may receive the charging request from the charging pile. In someembodiments, the charging request may be generated by the clientterminal. The processing device 112 (e.g., the charging managementdevice 420) may receive the charging request from the client terminal.

In 540, the processing device 110 (e.g., the charging management device420) may operate the charging pile at the target charging station tocharge the electric vehicle. In some embodiments, the processing device112 may determine charging information for charging the electric vehiclebased on the charging request and send the charging information to thecharging pile. The charging information may include one or morereference charging parameters, such as, reference charging volume,reference charging percentage, reference charging duration, referencecharging voltage, reference charging current, reference charging fee,etc. For example, the processing device 112 may determine the charginginformation for charging the electric vehicle based on the vehicleinformation. The charging pile may charge the electric vehicle based onthe charging information.

In some embodiments, the processing device 112 (e.g., the chargingmanagement device 420) may receive an association request for connectingthe processing device 112 and the client terminal. The processing device112 (e.g., the charging management device 420) may establish aconnection between the client terminal and the processing device 112based on the association request. In some embodiments, the processingdevice 112 (e.g., the charging management device 420) may determinewhether the charging for the electric vehicle is completed. If theprocessing device 112 (e.g., the charging management device 420)determines that the charging for the electric vehicle is completed, theprocessing device 112 (e.g., the charging management device 420) maydetermine a charging fee corresponding to the charging information andsending the charging fee to the client terminal based on the establishedconnection. The processing device 112 (e.g., the charging managementdevice 420) may further deduct the charging fee from an electronicfinancial account associated with the client terminal upon receiving apayment confirmation for the charging fee from the client terminal. Moredescriptions for controlling a charging pile to charge an electricvehicle may be in connection with the process 900 as described in FIG.9.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,operation 530 and operation 540 may be omitted. As another example,operation 510 and operation 520 may be omitted.

FIG. 6 is a block diagram illustrating an exemplary charging stationrecommendation device 410 according to some embodiments of the presentdisclosure. The charging station recommendation device 410 may include areceiving unit 610, a determining unit 620, a calculating unit 630, apushing unit 640, and a judging unit 650. The units of the chargingstation recommendation device 410 may be hardware circuits of at leastpart of the processing device 112. The units of the device 1400 may alsobe implemented as an application or set of instructions read andexecuted by the processing device 112. Further, the units may be anycombination of the hardware circuits and the application/instructions.For example, the units of the device 1400 may be the part of theprocessing device 112 when the processing device 112 is executing theapplication or set of instructions.

The receiving unit 610 may be configured to receive a request forcharging station recommendation from a client terminal (e.g., the clientterminal 130). The request for charging station recommendation may begenerated by the client terminal based on an input entered by a user ona user interface of the client terminal (e.g., the client terminal 130).

The determining unit 620 may be configured to determine at least onecharging station within a preset distance range of the client terminal.The preset distance range may be set and/or adjusted by a user oraccording to a default setting of the online to offline service system100. For example, if the determining unit 620 determines that there isno charging station or few charging stations within the preset distancerange, the determining unit 620 may increase the preset distance rangeto determine more charging stations.

The calculating unit 630 may be configured to determine an evaluationfor each of the at least one charging station based on one or moreevaluation parameters. The one or more evaluation parameters may includea price discount provided by the each of the at least one chargingstation, a distance between the each of the at least one chargingstation and the client terminal, a preset recommendation value for theeach of the at least one charging station, a historical evaluation ofthe each of the at least one charging station, or the like, or acombination thereof. In some embodiments, the evaluation of a chargingstation may be determined based on one or more preset weight valuescorresponding to the one or more evaluation parameters, respectively.

The pushing unit 640 may be configured to transmit the evaluation of theeach of the at least one charging station and an identifier of the eachof the at least one charging station to the client terminal. The pushingunit 640 may push the at least one charging station according to apredetermined strategy. For example, the charging station recommendationdevice 410 may sort the evaluation of the at least one charging stationin a descending order or an ascending order. Further, the chargingstation recommendation device 410 may send the evaluation of each of thesorted at least one charging station and the identifier of each of thesorted at least one charging station to the client terminal for display.

The judging unit 650 may be configured to determine whether theevaluation of the each of the at least one charging station is greaterthan or equal to a preset threshold. Further, the pushing unit 640 maysend the identifier of a target charging station the at least onecharging station to the client terminal for display in response to adetermination that the evaluation of the target charging station isgreater than or equal to the preset threshold.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example, thedetermining unit 620 and the calculating unit 630 may be integrated intoone single unit. As another example, the judging unit 650 may beintegrated into the calculating unit 650 or the determining unit 620.

FIG. 7 is a flowchart illustrating an exemplary process 500 for chargingstation recommendation according to some embodiments of the presentdisclosure. The process 700 may be executed by the system 100. Forexample, the process 700 may be implemented as a set of instructions(e.g., an application) stored in the storage device 150. The server 110(e.g., the charging station recommendation device 410) may execute theset of instructions and, when executing the instructions, it may beconfigured to perform the process 700. The operations of the illustratedprocess presented below are intended to be illustrative. In someembodiments, the process 700 may be accomplished with one or moreadditional operations not described and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofthe process as illustrated in FIG. 7 and described below is not intendedto be limiting.

In 710, the charging station recommendation device 410 (e.g., thereceiving unit 610) may receive a request for charging stationrecommendation from a client terminal (e.g., the client terminal 130).In some embodiments, the request for charging station recommendation maybe generated by the client terminal. For example, the request forcharging station recommendation may be generated based on an inputentered by a user via the client terminal (e.g., a user interface or anapplication). The client terminal may transmit the request for chargingstation recommendation to the charging station recommendation device 410via the network 120.

In 720, the charging station recommendation device 410 (e.g., thedetermining unit 620) may determine at least one charging station withina preset distance range of the client terminal. The preset distancerange may be shorter than a distance threshold, such as shorter than1000 meters, or 500 meters, or 100 meters, etc. The preset distancerange may be set and/or adjusted by a user or according to a defaultsetting of the online to offline service system 100. For example, if thecharging station recommendation device 410 determines that the number ofthe at least one charging station within the preset distance range islower than a quantity threshold, the charging station recommendationdevice 410 may increase the preset distance range to determine morecharging stations. The quantity threshold may be a constant, such as 0,1, 2, 3, etc.

In 730, the charging station recommendation device 410 (e.g. thecalculating unit 630) may evaluate each of the at least one chargingstation based on one or more evaluation parameters. The one or moreevaluation parameters may include a price discount provided by the eachof the at least one charging station, a distance between the each of theat least one charging station and the client terminal, a presetrecommendation value for the each of the at least one charging station,a historical evaluation of the each of the at least one chargingstation, a travel duration for arriving at the each of the at least onecharging station, a traffic condition associated with the each of the atleast one charging station, or the like, or a combination thereof. Insome embodiments, the evaluation of a charging station may be determinedbased on one or more preset weight values corresponding to the one ormore evaluation parameters, respectively. The charging stationrecommendation device 410 may estimate a weighted sum associated withthe one or more evaluation parameters based on the one or more presetweight values. The charging station recommendation device 410 maydesignate the weighted sum associated with the one or more evaluationparameters as the evaluation of the charging station.

In some embodiments, the preset weight value corresponding to anevaluation parameter may be a constant less than 1. The sum of the oneor more preset weight values may be equal to value 1. For example, theone or more preset weight values may include a first preset weight valuecorresponding to the price discount of the each of the at least onecharging station being 40%, a second preset weight value correspondingto the distance between the each of the at least one charging stationand the client terminal being 35%, a third preset weight valuecorresponding to the preset recommendation value of the each of the atleast one charging station being 20%, and a fourth preset weight valuecorresponding to the historical evaluation value of the each of the atleast one charging station being 5%.

In some embodiments, the preset weight values (e.g., the first presetweight value, the second preset weight value, the third preset weightvalue, and the fourth preset weight value) may be preset according tousers' preference by the user or the charging station recommendationdevice 410. For example, if the user prefers a specific evaluationparameters more particularly, the user or the charging stationrecommendation device 410 may adjust the preset weight valuecorresponding to the specific evaluation parameter. Further, if the userprefers the price discount of a charging station, the user may increasethe first preset weight value. The users' preference may be pre-analyzedbased on historical data relating to charging stations the user selectsor through questionnaires (or other forms).

In some embodiments, the charging station recommendation device 410 maydetermine the preset recommendation value of a charging station based onone or more recommendation parameters. The one or more recommendationparameters may include the number of charging piles of the chargingstation, a real-time parking fee at the charging station, a unitcharging price associated with the charging station, the number of freecharging piles at the charging station, or the like, or a combinationthereof.

In some embodiments, the charging station recommendation device 410 mayobtain one or more preset percentages corresponding to the one or morerecommendation parameters, respectively. Further, the charging stationrecommendation device 410 may determine the preset recommendation valuebased on the one or more preset percentages. The preset recommendationvalue may be equal to a sum of the one or more recommendation parametersmultiplying the corresponding preset percentages, respectively. In someembodiments, the preset percentage corresponding to a recommendationparameter may be a constant less than 1. The sum of the one or morepreset percentages may be equal to value 1. For example, the one or morepreset percentages may include a first preset percentage being 45%corresponding to the number of charging piles of the charging station, asecond preset percentage being 35% corresponding to the real-timeparking fee at the charging station, and a third preset percentage being20% corresponding to the charging unit price associated with thecharging station.

In some embodiments, the charging station recommendation device 410 maydetermine the preset recommendation value based on the one or morepreset percentages according to Equation (1) described as following:

R=Q×a%+P×b%+F×c%   (1),

where R refers to the preset recommendation value, Q refers to thenumber of charging piles, P refers to the real-time parking fee, Frefers to the charging unit price, a % refers to the first presetpercentage, b % refers to the second preset percentage, and c % refersto the third preset percentage.

In some embodiments, a first preset percentage corresponding to thenumber of charging piles of the charging station may be 45%. A secondpreset percentage corresponding to the real-time parking fee associatedwith the each of the at least one charging station may be 35%. A thirdpreset percentage corresponding to the charging unit price associatedwith the each of the at least one charging station may be 20%.

In this implementation, different charging stations may have differentcharacteristics including the number of charging piles, types, parkingfees, charging fee, etc. Therefore, the preset recommendation value maybe determined based on the recommendation parameters (e.g., the numberof the charging piles, the real-time parking fee, the charging unitprice, etc.) and the corresponding preset percentages. Therecommendation parameters (e.g., the number of the charging piles, thereal-time parking fee, or the charging unit price) having largerinfluence on the charging station recommendation may be allocated to alarger percentage, thereby improving calculation accuracy andreliability of the recommendation value.

In 740, the charging station recommendation device 410 (e.g., thepushing unit 640) may transmit the evaluation of the each of the atleast one charging station and an identifier of the each of the at leastone charging station to the client terminal 130. The evaluation of theeach of the at least one charging station and the identifier of the eachof the at least one charging station may be displayed by the clientterminal 130 (e.g., a user interface) for the user. The identifier of acharging station may be configured to identify and/or distinguish thecharging station from other charging stations. In some embodiments, theidentifier of a charging station may include a number of the chargingstation, an address of the charging station, a type of the chargingstation, etc.

In some embodiments, the charging station recommendation device 410(e.g., the pushing unit 640) may push information related to the atleast one charging station to the client terminal according to apredetermined strategy. For example, the charging station recommendationdevice 410 may sort the evaluation of the at least one charging stationin a descending order or an ascending order. In some embodiments, thecharging station recommendation device 410 may send the evaluation ofeach of the sorted at least one charging station and the identifier ofeach of the sorted at least one charging station to the client terminalfor display. In some embodiments, the charging station recommendationdevice 410 may determine the top specific number (e.g., the top one, thetop two, the top three, etc.) of charging stations and send the relatedinformation to the client terminal. In this implementation, the user canintuitively and accurately understand the at least one charging stationwithin the preset distance range and the corresponding identifiers. Theuser may arrange the at least one charging station according todifferent identifiers and select a charging station to charge his/hervehicle. For example, based on a user satisfaction rating of the atleast one charging station, the user can quickly and accuratelydetermine a charging station with better user satisfaction rating, whichimproves the user's convenience.

As another example, the charging station recommendation device 410(e.g., the determining unit 620) may determine whether the evaluation ofthe each of the at least one charging station is greater than or equalto a preset threshold. Further, the charging station recommendationdevice 410 may send the identifier of a target charging station from theat least one charging station to the client terminal for display inresponse to a determination that the evaluation of the target chargingstation is greater than or equal to the preset threshold. In thisimplementation, the user may more quickly obtain the most suitablecharging station among the at least one charging station, therebyimproving the user's experience and reducing the processing pressure ofthe server.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,process 700 may further include storing the evaluation of the each ofthe at least one charging station.

FIG. 8 is a block diagram illustrating an exemplary charging managementdevice 420 according to some embodiments of the present disclosure. Thecharging management device 420 may include a receiving unit 810, adetermining unit 620, a connecting unit 830, and sending unit 840. Theunits of the charging management device 420 may be hardware circuits ofat least part of the processing device 112. The units of the device 1400may also be implemented as an application or set of instructions readand executed by the processing device 112. Further, the units may be anycombination of the hardware circuits and the application/instructions.For example, the units of the device 420 may be the part of theprocessing device 112 when the processing device 112 is executing theapplication or set of instructions.

The receiving unit 810 may be configured to receive a charging requestfor charging an electric vehicle and an associating request from acharging pile. The charging request may include information relating tothe electric vehicle. For example, the information relating to theelectric vehicle may include the license number of the electric vehicle,the type of the electric vehicle, the current dump energy of theelectric vehicle, the type of a charger for the electric vehicle, etc.The associating request may be used for connecting a client terminal(e.g., the client terminal 130) associated with the electric vehicle(e.g., the electric vehicle 140) and the charging management device 420.The associating request may include identification information relatingto the client terminal.

The determining unit 820 may be configured to determine charginginformation for charging the electric vehicle associated with the clientterminal based on the charging request. The charging information mayinclude one or more reference charging parameters, such as, referencecharging volume, reference charging percentage, reference chargingduration, reference charging voltage, reference charging current,reference charging fee, etc. For example, the determining unit 820 maydetermine the reference charging duration, reference charging fee, andreference charging volume based on the current dump energy of theelectric vehicle. As another example, the determining unit 820 maydetermine the reference charging voltage based on the type of theelectric vehicle or the type of the charger for the electric vehicle.

The connecting unit 830 may be configured to establish a connectionbetween the charging management device and the client terminal. In someembodiments, the connection between the charging management device andthe client terminal may be generated via a wireless connection, such asthe network 120.

The sending unit 840 may be configured to send the charging informationto the charging pile for charging the electric vehicle based on thecharging information. In some embodiments, the sending unit 840 may sendthe charging information to the client terminal through the connectionbetween the charging management device 420 and the client terminal.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example, thereceiving unit 810 and the sending unit 840 may be integrated into onesingle unit.

FIG. 9 is a flowchart illustrating an exemplary process 900 foroperating a charging pile to charge an electric vehicle according tosome embodiments of the present disclosure. The process 900 may beexecuted by the online to offline service system 100. For example, theprocess 900 may be implemented on a processing device (e.g., thecharging management device 420) having a processor, at least one storagedevice and a data exchange port communicatively connected to a network.The process 900 may be implemented as a set of instructions (e.g., anapplication) stored in the storage device 150. The processing device 112(e.g., the charging management device 420) may execute the set ofinstructions and, when executing the instructions, it may be configuredto perform the process 900. The operations of the illustrated processpresented below are intended to be illustrative. In some embodiments,the process 900 may be accomplished with one or more additionaloperations not described and/or without one or more of the operationsdiscussed. Additionally, the order in which the operations of theprocess as illustrated in FIG. 9 and described below is not intended tobe limiting.

In 910, the charging management device 420 (e.g., the receiving unit810) may receive a charging request for charging an electric vehicle andan associating request from a charging pile. The charging request mayinclude information relating to the electric vehicle. For example, theinformation relating to the electric vehicle may include the licensenumber of the electric vehicle, the type of the electric vehicle, thecurrent dump energy of the electric vehicle, the type of a charger forthe electric vehicle, etc. The associating request may be used forconnecting a client terminal (e.g., the client terminal 130) associatedwith the electric vehicle (e.g., the electric vehicle 140) and thecharging management device 420 for communication via a network. Theassociating request may include identification information relating tothe client terminal. The identification information relating to theclient terminal may be configured to distinguish the client terminalfrom others, for example, the MAC address of the client terminal, theIMEI of the client terminal, the Pseudo-Unique ID, the Android ID, orthe like, or a combination thereof.

In some embodiments, the charging request and/or the associating requestmay be generated by the charging pile. For example, if the charging piledetects that the electric vehicle is connected to the charging pile viaa physical connection (e.g., a wired connection), the charging pile maygenerate the charging request and/or the associating request. In someembodiments, the charging request and/or the associating request may begenerated by the client terminal when the electric vehicle is connectedto the charging pile via a physical connection (e.g., a wiredconnection). The physical connection between the electric vehicle andthe charging pile may be identified as a trigger signal to betransmitted to the client terminal. The client terminal may be triggeredto generate the charging request and/or the associating request by thetrigger signal. In some embodiments, the charging request and/or theassociating request may be generated by the client terminal based on aninput entered by a user via a user interface of the client terminal 130.The client terminal 130 may send the charging request and theassociating request to the charging pile via the network 120. Moredescriptions for generating the charging request and/or the associatingrequest by the client terminal may be found elsewhere in the presentdisclosure (e.g., FIG. 11 and the descriptions thereof).

In 920, the charging management device 420 (e.g., the determining unit820) may determine charging information for charging the electricvehicle associated with the client terminal based on the chargingrequest. The charging information may include one or more referencecharging parameters, such as, a reference charging volume, a referencecharging percentage, a reference charging duration, a reference chargingvoltage, a reference charging current, a reference charging fee, etc.For example, the charging management device 420 (e.g., the determiningunit 820) may determine the reference charging duration, the referencecharging fee, and/or the reference charging volume based on the currentdump energy of the electric vehicle. As another example, the chargingmanagement device 420 (e.g., the determining unit 820) may determine thereference charging voltage based on the type of the electric vehicle orthe type of the charger for the electric vehicle.

In 930, the charging management device 420 (e.g., the connecting unit830) may establish a connection between the charging management device420 and the client terminal based on the associating request. In someembodiments, the connection between the charging management device 420and the client terminal may be generated via a wireless connection, suchas the network 120. The charging management device 420 may communicatewith the client terminal via the connection. For example, the chargingmanagement device 420 may send the charging fee for charging theelectric vehicle to the client terminal. As another example, thecharging management device 420 may deduct the charging fee from anelectric bank account associated with the client terminal.

In 940, the charging management device 420 (e.g., the sending unit 840)may send the charging information to the charging pile for charging theelectric vehicle based on the charging information. In some embodiments,the charging pile may send the charging information to the clientterminal after receiving the charging information from the chargingmanagement device 420. In some embodiments, the charging managementdevice 420 (e.g., the sending unit 840) may send the charginginformation to the client terminal through the connection between thecharging management device 420 and the client terminal. The user mayadjust the charging information determined by the charging managementdevice 420 via a user interface implemented on the client terminaland/or the charging pile. For example, the user may adjust one or morereference charging parameters (e.g., the reference charging duration,the reference charging volume, etc.) according to user' actual demands.

In this embodiment, the charging management device 420 may determine thecharging information of the electric vehicle, and directly send thecharging information to the charging pile, such that the user canconveniently set the charging information through the client terminal orthe charging pile, and the user's experience may be improved.

In 950, the charging management device 420 may operate the charging pilefor charging the electric vehicle based on the charging information. Insome embodiments, the charging management device 420 may generate acharging signal for starting to charge the electric vehicle aftertransmitting the charging information to the charging pile. The chargingmanagement device 420 may transmit the charging signal to the chargingpile and/or the client terminal for display. The charging may be startedby the user manually or the charging management device 420 in responseto a confirmation for the charging signal from the client terminal.

In some embodiments, the charging management device 420 may obtain acurrent charging status that the charging pile 160 charges the electricvehicle 140. The charging management device 420 may send the currentcharging status to the client terminal through the connection betweenthe client terminal 130 and the charging management device 420. Thecurrent charging status may include current charging volume, currentcharging percentage, current charging duration, current charging fee,etc.

In some embodiments, the charging management device 420 may determinewhether the charging for the electric vehicle is completed. The chargingmanagement device 420 may determine whether the charging for theelectric vehicle is completed based on the current charging status andthe charging parameters. For example, the charging management device 420may determine that the charging for the electric vehicle is completed ifthe charging management device 420 determines that the current chargingduration is equal to the reference charging duration. As anotherexample, the charging management device 420 may determine that thecharging for the electric vehicle is completed if the chargingmanagement device 420 receives a stop charging instruction from theclient terminal. In response to a determination that the charging forthe electric vehicle is completed, the charging management device 420may determine a charging fee corresponding to the charging information.For example, the charging management device 420 may determine thereference charging fee as the charging fee if the charging managementdevice 420 determines that the current charging duration (or the currentcharging volume) is equal to the reference charging duration(or thereference charging volume). As another example, the charging managementdevice 420 may determine the current charging fee as the charging fee ifthe charging management device 420 receives the stop charginginstruction from the client terminal. The charging management device 420may send the charging fee to the client terminal via the connectionbetween the client terminal and the charging management device 420. Thecharging management device 420 may deduct the charging fee from anelectronic financial account associated with the client terminal uponreceiving a payment confirmation for the charging fee from the clientterminal. In some embodiments, the user may pre-pay a certain amount ofmoney for charging the electric vehicle. The charging fee issimultaneously deducted from the pre-paid amount during the charging,and the charging management device 420 may determine that the chargingfor the electric vehicle is completed once the remaining balance of thepre-paid amount reaches zero.

In addition, by receiving the associating request from the chargingpile, the charging management device 420 may initiatively establish aconnection with the client terminal 130. Therefore, the associatingoperations to establish the connection between the client terminal andthe charging management device 420 that need to be performed by theclient terminal is eliminated, and thus, simplifying the operations ofthe client terminal and improving the charging efficiency. Because theconnection between the charging management device 420 and the clientterminal is initiated by the charging management device 420, it is alsobeneficial to improve security of the user's account (e.g., an electricbank account).

Particularly, the physical connection between the charging pile and theelectric vehicle may be recognized by the electric vehicle as a triggersignal (e.g., an electric signal of a high level or a high voltage). Theelectric vehicle may send the trigger signal to the client terminalassociated with the electric vehicle. The trigger signal may be used totrigger the client terminal to generate the associating request and thecharging request. Before the communication connection is establishedbetween the client terminal and the charging management device 420,since the client terminal does not know a communication address of thecharging management device 420, the associating request and the chargingrequest may be sent to the charging management device 420 through thecharging pile.

In some embodiments, the user may input the charging request via theclient terminal. The client terminal may generate the associatingrequest automatically when detecting the charging request to betransmitted to the charging pile. The charging request and theassociating request may be transmitted to the charging pile by theclient terminal. And the charging pile may send the charging request andthe associating request to the charging management device 420 before theclient terminal is connected with the charging management device 420.The charging management device 420 may determine the charginginformation based on the charging request, and operate the charging pileto charge the electric vehicle according to the charging information.The charging management device 420 may also establish the connectionwith the client terminal according to the association request.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,operation 920 and operation 930 may be performed synchronously. Asanother example, operation 930 and operation 940 may be performedsynchronously. In some embodiments, process 900 may further includestoring the charging information for charging the electric vehicle.

FIG. 10 is a block diagram illustrating an exemplary processor 1000 of acharging pile according to some embodiments of the present disclosure.The processor 1000 may include a determining unit 1010, a sending unit1020, and receiving unit 1030. The units of the processor 1000 may behardware circuits of at least part of the computing device 300. Theunits of the processor 1000 may also be implemented as an application orset of instructions read and executed by the computing device 300.Further, the units may be any combination of the hardware circuits andthe application/instructions. For example, the units of the processor1000 may be the part of the computing device 300 when the computingdevice 300 is executing the application or set of instructions.

The determining unit 1010 may be configured to determine whether thecharging pile is connected with an electric vehicle. In someembodiments, the electric vehicle may include a charging interface. Theprocessor may determine that the charging pile is connected with theelectric vehicle if the processor detects the charging interface. Insome embodiments, the determining unit 1010 may determine a clientterminal associated with the electric vehicle in response to adetermination that the charging pile is connected with the electricvehicle. After detecting the charging interface of the electric vehicle,the processor may actively obtain vehicle information of the electricvehicle via the charging interface. The vehicle information of theelectric vehicle may include the license number of the electric vehicle,the type of the electric vehicle, the current dump energy of theelectric vehicle, the type of a charger for the electric vehicle, etc.The processor may determine information relating to a client terminalthat is associated with the electric vehicle based on the vehicleinformation. The information relating to the client terminal may includeidentification information of the client terminal, such as the MACaddress of the client terminal, the IMEI of the client terminal, thePseudo-Unique ID, the Android ID, or the like, or a combination thereof.The processor may further determine the associated client terminal basedon the information relating to the client terminal. The associatingoperations between the client terminal and the charging pile may besimplified by determining the information relating to the clientterminal based on the vehicle information, and the user's experience isimproved.

The sending unit 1020 may be configured to send a charging prompt and anassociating prompt to the client terminal. The charging prompt mayinclude the vehicle information relating to the electric vehicleobtained by the charging pile. The client terminal may display thecharging prompt to prompt a user. In some embodiments, the user mayadjust the vehicle information based on a user interface of the clientterminal. The client terminal may generate a charging request includethe adjusted vehicle information. The associating prompt may include theinformation relating to the client terminal determined by the chargingpile. The client terminal may display the associating prompt to promptthe user. In some embodiments, the user may adjust the informationrelating to the client terminal via the user interface of the clientterminal. The client terminal may generate an associating requestinclude the adjusted information relating to the client terminal.

The receiving unit 1030 may be configured to receive a charging requestand an associating request from the client terminal. The chargingrequest may be used for charging the electric vehicle at the chargingpile. The charging request may include the adjusted vehicle informationrelating to the electric vehicle. For example, the adjusted vehicleinformation relating to the electric vehicle may include the licensenumber of the electric vehicle, the type of the electric vehicle, thecurrent dump energy of the electric vehicle, the type of a charger forthe electric vehicle, etc. The associating request may be used forconnecting the client terminal (e.g., the client terminal 130)associated with the electric vehicle (e.g., the electric vehicle 140)and a charging management device (e.g., the charging management device420). The associating request may include the adjusted informationrelating to the client terminal. The adjusted information relating tothe client terminal may include the MAC address of the client terminal,the NEI of the client terminal, the Pseudo-Unique ID, the Android ID, orthe like, or a combination thereof.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,processor 1000 may further include a judging unit. As another example,the sending unit 1020 and the receiving unit 1030 may be integrated intoone single unit.

FIG. 11 is a flowchart illustrating an exemplary process 1100 forcharging an electric vehicle 140 according to some embodiments of thepresent disclosure. The process 1100 may be executed by the online tooffline service system 100. For example, the process 1100 may beimplemented on a charging pile (e.g., a charging pile at the chargingstation 160) having a processor, at least one storage device and a dataexchange port communicatively connected to a network. The process 1100may be implemented as a set of instructions (e.g., an application)stored in the at least one storage device. The processor of the chargingpile may execute the set of instructions and, when executing theinstructions, it may be configured to perform the process 1100. Theoperations of the illustrated process presented below are intended to beillustrative. In some embodiments, the process 1100 may be accomplishedwith one or more additional operations not described and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of the process as illustrated in FIG. 11 and describedbelow is not intended to be limiting.

In 1110, the processor (e.g., the determining unit 1010) may determinewhether the charging pile is connected with an electric vehicle (e.g.,the electric car 140-1). In some embodiments, the electric vehicle mayinclude a charging interface. The processor may determine that thecharging pile is connected with the electric vehicle if the processordetects the charging interface. In some embodiments, the processor(e.g., the determining unit 1010) may determine whether the chargingpile is connected with the electric vehicle (e.g., the electric car140-1) based on a video monitoring system configured to monitor a regionsurrounding the charging pile. For example, the video monitoring systemmay acquire image data associated with the charging pile and transferthe image data to the processor. The processor may determine whether thecharging pile is connected with the electric vehicle based on the imagedata.

In 1120, the processor (e.g., the determining unit 1010) may determine aclient terminal associated with the electric vehicle in response to adetermination that the charging pile is connected with the electricvehicle. After detecting the charging interface of the electric vehicle,the processor may actively obtain vehicle information of the electricvehicle via the charging interface and/or the data exchange port of thecharging pile. The vehicle information of the electric vehicle mayinclude the license number of the electric vehicle, the type of theelectric vehicle, the current dump energy of the electric vehicle, thetype of a charger for the electric vehicle, etc. The processor mayfurther determine information relating to the client terminal that isassociated with the electric vehicle. The information relating to theclient terminal may include identification information of the clientterminal, such as the MAC address of the client terminal, the NEI of theclient terminal, the Pseudo-Unique ID, the Android ID, or the like, or acombination thereof. In some embodiments, the client terminal may beconnected to the electric vehicle via a wireless connection (e.g.,Bluetooth) or a wired connection (e.g., a charging line). The processormay determine information relating to the client terminal based on theconnection between the client terminal and the electric vehicle.

The processor may further determine the associated client terminal basedon the information relating to the client terminal. The associatingoperations between the client terminal and the charging pile may besimplified by determining the information relating to the clientterminal based on the vehicle information, and therefore, the user'sexperience is improved.

In 1130, the processor (e.g., the sending unit 1020) may send a chargingprompt and an associating prompt to the client terminal. In someembodiments, the charging prompt may include the vehicle informationrelating to the electric vehicle obtained by the charging pile. Theclient terminal may display the charging prompt to prompt the user. Insome embodiments, the user may adjust the vehicle information based on auser interface of the client terminal. The client terminal may generatea charging request including the vehicle information (or the adjustedvehicle information) relating to the electric vehicle. The associatingprompt may include the information relating to the client terminaldetermined by the charging pile. The client terminal may display theassociating prompt to prompt the user. In some embodiments, the user mayadjust the information relating to the client terminal via the userinterface of the client terminal. The client terminal may generate anassociating request include the information (or the adjustedinformation) relating to the client terminal.

In 1140, the processor (e.g., the receiving unit 1030) may receive acharging request and an associating request from the client terminal.The charging request may be used for charging the electric vehicle atthe charging pile. The charging request may include the vehicleinformation (or the adjusted vehicle information) relating to theelectric vehicle. For example, the vehicle information relating to theelectric vehicle may include the license number of the electric vehicle,the type of the electric vehicle, the current dump energy of theelectric vehicle, the type of a charger for the electric vehicle, etc.The associating request may be used for connecting the client terminal(e.g., the client terminal 130) associated with the electric vehicle(e.g., the electric vehicle 140) and a charging management device (e.g.,the charging management device 420) for communication via a network. Theassociating request may include the information (or the adjustedinformation) relating to the client terminal. The information relatingto the client terminal may include the MAC address of the clientterminal, the IMEI of the client terminal, the Pseudo-Unique ID, theAndroid ID, or the like, or a combination thereof. In some embodiments,the charging request and the associated request may be displayed on auser interface implemented on the charging pile. The user may confirmthe charging request and the associating request again before theprocessor sends the charging request and the associated request to thecharging management device (e.g., the charging management device 420).

In 1150, the processor may send the charging request and the associatingrequest to a charging management device via the data exchange port. Insome embodiments, the charging management device (e.g., the chargingmanagement device 420) may determine charging information for chargingthe electric vehicle based on the charging request as describedelsewhere in the present disclosure (e.g., FIG. 9 and the descriptionsthereof). The charging information may include one or more referencecharging parameters, such as, a reference charging volume, a referencecharging percentage, a reference charging duration, a reference chargingvoltage, a reference charging current, a reference charging fee, etc.The charging management device (e.g., the charging management device420) may transmit the charging information to the charging pile forcharging the electric vehicle. In some embodiments, the chargingmanagement device (e.g., the charging management device 420) mayestablish a connection between the charging management device and theclient terminal based on the associating request.

In some embodiments, the process 1100 (e.g., the receiving unit 1010)may further include receiving the charging information from the chargingmanagement device. The processor may operate the charging pile to chargethe electric vehicle 140 based on the charging information. Moredescriptions for charging the electric vehicle may be found elsewhere inthe present disclosure (e.g., FIG. 14, and the descriptions thereof).

In some embodiments, the process 1100 (e.g., the sending unit 1020) mayfurther include obtaining and sending a current charging status of theelectric vehicle to the charging management device 420. The chargingmanagement device 420 may determine whether the charging for theelectric vehicle is completed based on the current charging status ofthe electric vehicle. If the charging management device 420 determinesthat the charging for the electric vehicle is completed, the chargingmanagement device 420 may stop the charging pile to charge the electricvehicle. Further, the charging management device 420 may determine acharging fee and send the charging fee to the client terminal and/or thecharging pile. Upon receiving a payment confirmation from the chargingpile or the client terminal, the charging management device 420 maydeduct the charging fee from an electric bank account associated withthe client terminal.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,operation 1130 and operation 1140 may be omitted. Process 1100 mayinclude generating the charging request and the associating request bythe processor of the charging pile.

FIG. 12 is a block diagram illustrating an exemplary processor 1200implemented on the client terminal 130 according to some embodiments ofthe present disclosure. The processor may include a receiving unit 1210,a displaying unit 1220, a generating unit 1230, and a sending unit 1240.The units of the processor 1200 may be hardware circuits of at leastpart of the mobile device 200. The units of the processor 1200 may alsobe implemented as an application or set of instructions read andexecuted by the mobile device 200. Further, the units may be anycombination of the hardware circuits and the application/instructions.For example, the units of the processor 1200 may be the part of themobile device 200 when the mobile device 200 is executing theapplication or set of instructions.

The receiving unit 1210 may be configured to receive a charging promptand an associating prompt from a charging pile via a data exchange portafter the charging pile is connected to an electric vehicle associatedwith the client terminal. The charging prompt may include vehicleinformation relating to the electric vehicle obtained by the chargingpile as described elsewhere in the present disclosure (e.g., FIG. 11 andthe descriptions thereof). The associating prompt may includeinformation relating to the client terminal determined by the chargingpile as described elsewhere in the present disclosure (e.g., FIG. 11 andthe descriptions thereof). The charging pile may send the chargingprompt and the associating prompt to the client terminal.

The displaying unit 1220 may be configured to cause a user interface ofthe client terminal 130 to display the charging prompt and/or theassociating prompt. In some embodiments, the client terminal 130 maydisplay the charging prompt and/or the associating prompt on the userinterface in the form of text or image. In some embodiments, the clientterminal 130 may display the charging prompt and/or the associatingprompt to the user via a message in the form of text, voice, image, etc.

The generating unit 1230 may be configured to generate a chargingrequest for charging the electric vehicle based on a user interaction onthe user interface. The charging request may be inputted by the user onthe user interface. In some embodiments, the user may adjust the vehicleinformation based on the user interaction on the user interface. Theclient terminal may generate the charging request include the adjustedvehicle information. In some embodiments, the generating unit 1230 maybe configured to generate an associating request for connecting theclient terminal with a charging management device based on theassociating prompt. The associating request may be used for connectingthe client terminal with the charging management device (e.g., thecharging management device 420). In some embodiments, the user mayadjust the information relating to the client terminal via the userinterface of the client terminal. The client terminal may generate theassociating request including the adjusted information relating to theclient terminal.

The sending unit 1240 may be configured to send the charging request andthe associating request to the charging pile. The charging pile maytransmit the charging request and the associating request to thecharging management device. The charging management device may generatecharging information for charging the electric vehicle and the send thecharging information to the charging pile. The charging pile may chargethe electric vehicle based on the charging information as describedelsewhere in the present disclosure (e.g., FIG. 11, and the descriptionsthereof).

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example, thesending unit 1040 and the receiving unit 1210 may be integrated into onesingle unit.

FIG. 13 is a flowchart illustrating an exemplary process 1300 forcharging an electric vehicle according to some embodiments of thepresent disclosure. The process 1300 may be executed by the online tooffline service system 100. For example, the process 1300 may beimplemented on a client terminal (e.g., the client terminal 130) havinga processor, at least one storage device and a data exchange portcommunicatively connected to a network. The process 1300 may beimplemented as a set of instructions (e.g., an application) stored inthe at least one storage device. The processor of client terminal mayexecute the set of instructions and, when executing the instructions, itmay be configured to perform the process 1300. The operations of theillustrated process presented below are intended to be illustrative. Insome embodiments, the process 1300 may be accomplished with one or moreadditional operations not described and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofthe process as illustrated in FIG. 13 and described below is notintended to be limiting.

In 1310, the processor (e.g., the receiving unit 1210) may receive acharging prompt and an associating prompt from a charging pile via adata exchange port after the charging pile is connected to an electricvehicle associated with a client terminal. In some embodiments, thecharging pile may be connected to the electric vehicle via a charginginterface connected with the electric vehicle. The charging prompt andthe associating prompt may be generated by the charging pile after thecharging pile detects the charging interface. The charging prompt mayinclude vehicle information relating to the electric vehicle obtained bythe charging pile as described elsewhere in the present disclosure(e.g., FIG. 11 and the descriptions thereof). The associating prompt mayinclude information relating to the client terminal determined by thecharging pile as described elsewhere in the present disclosure (e.g.,FIG. 11 and the descriptions thereof). The charging pile may send thecharging prompt and the associating prompt to the client terminal.

In 1320, the processor (e.g., the displaying unit 1220) may cause a userinterface of the client terminal 130 to display the charging promptand/or the associating prompt. In some embodiments, the client terminal130 may display the charging prompt and/or the associating prompt on theuser interface in the form of text or image. In some embodiments, theclient terminal 130 may display the charging prompt and/or theassociating prompt to the user via a message in the form of text, voice,image, etc.

In 1330, the processor (e.g., the generating unit 1230) may generate acharging request for charging the electric vehicle based on a userinteraction on the user interface. In some embodiments, the chargingrequest may be inputted by the user via the user interface. In someembodiments, the user may adjust the vehicle information relating to theelectric vehicle based on the user interaction on the user interface.The client terminal may generate the charging request include theadjusted vehicle information.

In 1340, the processor (e.g., the generating unit 1230) may generate anassociating request for connecting the client terminal with a chargingmanagement device based on the associating prompt. The associatingrequest may be used for connecting the client terminal with the chargingmanagement device (e.g., the charging management device 420). In someembodiments, the user may adjust the information relating to the clientterminal via the user interface of the client terminal. The clientterminal may generate the associating request including the adjustedinformation relating to the client terminal.

In 1350, the processor (e.g., the sending unit 1240) may send thecharging request and the associating request to the charging pile. Insome embodiments, the processor (e.g., the sending unit 1240) may sendthe charging request and the associating request to the charging pilevia the data exchange port communicatively connected to a network (e.g.,the network 120). The charging pile may further transmit the chargingrequest and the associating request to the charging management device.The charging management device may generate charging information forcharging the electric vehicle and the send the charging information tothe charging pile. The charging information for charging the electricvehicle may include one or more reference charging parameters asdescribed elsewhere in the present disclosure. The charging pile maycharge the electric vehicle based on the charging information asdescribed elsewhere in the present disclosure (e.g., FIG. 11, and thedescriptions thereof).

In some embodiments, the client terminal may receive a current chargingstatus of the electric vehicle sent by the charging management device orthe charging pile. The client terminal may display the current chargingstatus on the user interface implemented on the client terminal and/orthe charging pile for a user.

In some embodiments, the client terminal may generate and/or receive astop charging request based on an input of the user via the userinterface. For example, the user may click a stop button associated withthe stop charging request on the user interface. Then the clientterminal may generate the stop charging request.

In some embodiments, the client terminal may receive a charging feegenerated and sent by the charging management device. The chargingmanagement device may determine the charging fee based on the charginginformation and/or the current charging status. For example, thecharging fee may be equal to the reference charging fee or the currentcharging fee as described in FIG. 9. Further, the charging managementdevice may send the calculated charging fee to the client terminal. Theclient terminal may display the calculated charging fee on the userinterface for the user. The client terminal may obtain a paymentconfirmation for the charging fee from the user interface by the user.For example, the user may click a button associated with the paymentconfirmation on the user interface to generate the payment confirmation.The client terminal may send the payment confirmation to the chargingmanagement device causing the charging management device to deduct thecharging fee from an electronic bank account associated with the clientterminal.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,operation 1330 and operation 1340 may be performed synchronously.

FIG. 14 is a flowchart illustrating an exemplary process 1400 forcharging an electric vehicle according to some embodiments of thepresent disclosure. The process 1400 may be executed by the online tooffline service system 100. For example, the process 1400 may beimplemented on a charging pile (e.g., a charging pile at the chargingstation 160) having a processor, at least one storage device and a dataexchange port communicatively connected to a network. The process 1100may be implemented as a set of instructions (e.g., an application)stored in the at least storage device. The processor of the chargingpile may execute the set of instructions and, when executing theinstructions, it may be configured to perform the process 1400. Theoperations of the illustrated process presented below are intended to beillustrative. In some embodiments, the process 1400 may be accomplishedwith one or more additional operations not described and/or without oneor more of the operations discussed. Additionally, the order in whichthe operations of the process as illustrated in FIG. 14 and describedbelow is not intended to be limiting. In some embodiments, process 1100may further include operations 1410 to 1440.

In 1410, the processor (e.g., the receiving unit 1030) may obtainvehicle information of an electric vehicle that is connected to thecharging pile 160 via a physical connection. The physical connection mayinclude a wired connection (e.g., the charging line). In someembodiments, the electric vehicle may include a charging interface. Thecharging pile may be connected to the electric vehicle via the charginginterface. In some embodiments, the processor may obtain the vehicleinformation via the charging interface. In some embodiments, theprocessor may establish a connection between the charging pile and theclient terminal via the network (e.g., the network 120) when theprocessor detects the charging interface. Further the processor mayobtain the vehicle information from the electric vehicle via the dataexchange port communicatively connected to the network (e.g., thenetwork 120). The vehicle information may be stored in a storage deviceimplemented on the electric vehicle. The vehicle information of theelectric vehicle may include the type of the electric vehicle, the brandof the electric vehicle, the license number of the electric vehicle, acurrent dump energy of the electric vehicle, the type of a charger ofthe electric vehicle, or the like.

In 1420, the processor (e.g., the sending unit 1020) may send a queryinstruction to a charging management device based on the vehicleinformation. The query instruction may be used to obtain charginginformation corresponding to the vehicle information. The queryinstruction may include a charging request and/or an associating requestas described elsewhere in the present disclosure. The charging requestmay include the vehicle information. The associating request may includeinformation relating to the client terminal. The information relating tothe client terminal may include identification information of the clientterminal, such as the MAC address of the client terminal, the IMEI ofthe client terminal, the Pseudo-Unique ID, the Android ID, or the like,or a combination thereof.

In 1430, the processor (e.g., the receiving unit 1030) may receivecharging information corresponding to the vehicle information and acharging signal. The charging management device may estimate and/orsearch the charging information based on the vehicle information. Thecharging information may include one or more reference chargingparameters such as reference charging duration, reference chargingvoltage, reference charging current, reference charging volume, etc., asdescribed elsewhere in the present disclosure. For example, the chargingmanagement device may determine the reference charging current based onthe type of the electric vehicle. As another example, the chargingmanagement device may estimate a reference charging duration or volumebased on the current dump energy of the electric vehicle. The chargingmanagement device may transmit the charging information to the chargingpile.

The charging signal may be a confirmation for starting to charge theelectric vehicle from the client terminal. In some embodiments, thecharging management device may generate a control instruction forstarting the charging pile. The charging management device may transmitthe control instruction for starting the charging pile to the clientterminal. The client terminal may display the control instruction to theuser and generate the charging signal upon receiving a confirmation forstarting the charging pile form the user.

In 1440, the processor (e.g., the determining unit 1010) may operate thecharging pile to charge the electric vehicle based on the charginginformation. In some embodiments, after the processor receives thecharging information from the charging management device, the processormay start the charging pile to charge the electric vehicle. In someembodiments, after the processor receives the charging information fromthe charging management device, the processor may generate a prompt forstarting to charge the electric vehicle. In some embodiments, the promptfor starting to charge the electric vehicle may be displayed on a userinterface of the charging pile. In some embodiments, the prompt forstarting to charge the electric vehicle may be transmitted to the clientterminal for displaying to the user. In some embodiments, the processormay start the charging pile to charge the electric vehicle uponreceiving a confirmation for the prompt for starting to charge theelectric vehicle from the user. In some embodiments, the user may startthe charging pile manually after receiving the prompt for starting tocharge the electric vehicle.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure. For example,process 1400 may further include determining information relating to theclient terminal and determining the client terminal associated with theelectric vehicle based on the information relating to the clientterminal.

FIG. 15 is a flowchart illustrating an exemplary process 1500 forcharging an electric vehicle 140 according to some embodiments of thepresent disclosure. The process 1500 may be executed by the online tooffline service system 100. For example, the process 1500 may beimplemented on a processing device (e.g., the charging management device420) having a processor, at least one storage device and a data exchangeport communicatively connected to a network. The process 1500 may beimplemented as a set of instructions (e.g., an application) stored inthe storage device 150. The charging management device 420 may executethe set of instructions and, when executing the instructions, it may beconfigured to perform the process 1500. The operations of theillustrated process presented below are intended to be illustrative. Insome embodiments, the process 1500 may be accomplished with one or moreadditional operations not described and/or without one or more of theoperations discussed. Additionally, the order in which the operations ofthe process as illustrated in FIG. 15 and described below is notintended to be limiting. In some embodiments, process 900 may furtherinclude operations 1510 to 1550.

In 1510, the charging management device 420 (e.g., the receiving unit810) may receive a query instruction from a charging pile 160. The queryinstruction may include a charging request and/or an associating requestas described elsewhere in the present disclosure. The charging requestmay include the vehicle information for charging an electric vehicle.The associating request may include information relating to the clientterminal for connecting the charging management device 420 with a clientterminal associated with the electric vehicle. The information relatingto the client terminal may include identification information of theclient terminal, such as the MAC address of the client terminal, theIMEI of the client terminal, the Pseudo-Unique ID, the Android ID, orthe like, or a combination thereof.

In 1520, the charging management device 420 (e.g., the determining unit820) may determine a corresponding client terminal based on the queryinstruction. In some embodiments, the charging management device 420(e.g., the determining unit 820) may determine the corresponding clientterminal based on the associating request. Further, the chargingmanagement device 420 (e.g., the determining unit 820) may determine thecorresponding client terminal based on the information relating to theclient terminal. In some embodiments, the charging management device 420may establish a connection between the charging management device 420and the corresponding client terminal via a network (e.g., the network120).

In 1530, the charging management device 420 (e.g., the sending unit 840)may send a control instruction for starting a charging pile to thecorresponding client terminal. In some embodiments, the chargingmanagement device 420 may send the control instruction to thecorresponding client terminal via the data exchange port communicativelyconnected to the network (e.g., the network 120).

In 1540, the charging management device 420 (e.g., the receiving unit810) may receive a charging signal from the corresponding clientterminal. The corresponding client terminal may display the controlinstruction to the user and generate the charging signal upon receivinga confirmation for starting the charging pile form the user.

In 1550, the charging management device 420 (e.g., the sending unit 840)may send the charging signal to the charging pile causing the chargingpile to charge the electric vehicle 140. After the charging pilereceives the charging signal, the charging pile may start to charge theelectric vehicle. In some embodiments, the charging management device420 may generate charging information for charging the electric vehicle.The charging pile may charge the electric vehicle based on the charginginformation.

It should be noted that the above description is merely provided for thepurposes of illustration, and not intended to limit the scope of thepresent disclosure. For persons having ordinary skills in the art,multiple variations and modifications may be made under the teachings ofthe present disclosure. However, those variations and modifications donot depart from the scope of the present disclosure.

FIG. 16 shows a schematic diagram illustrating a charging process 1600according to some embodiments of the present disclosure. As shown inFIG. 16, a user may connect a client terminal 1630 with an electricvehicle 1610 via a network (e.g., the network 120). Associatinginformation relating to the election vehicle 1610 and the clientterminal 1620 may be generated. The associating information may includevehicle information relating to the electric vehicle 1610 andinformation relating to the corresponding client terminal 1620. When theelectric vehicle 1610 is physically connected to a charging pile 1620via a charging interface implemented on the electric vehicle 1610, thecharging pile 1620 may transmit an associating request for connecting aserver 1640 and the client terminal 1630 and a charging request forcharging the electric vehicle 1610 to the server 1640. Then the server1640 may generate charging information based on the charging request andsend the charging information to the charging pile 1620. The chargingpile 1620 may charge the electric vehicle 1610 based on the charginginformation. In some embodiments, the server 1640 may receive currentcharging status of the electric vehicle 1610 from the charging pile1620. The server 1640 may determine a charging fee based on the charginginformation and/or the current charging status. The server 1640 maytransmit the received current charging status and/or the charging fee tothe client terminal 1630. The server 1640 may deduct the charging feefrom an electric bank account associated with the client terminal 1630.In some embodiments, the user may input a stop charging instruction viathe client terminal 1630 to the charging pile 1620 and/or the server1640. The charging pile 1620 may stop to charge the electric vehicle1610 in response to the stop charging instruction.

To implement various modules, units, and their functionalities describedin the present disclosure, computer hardware platforms may be used asthe hardware platform(s) for one or more of the elements describedherein. A computer with user interface elements may be used to implementa personal computer (PC) or any other type of work station or terminaldevice. A computer may also act as a server if appropriately programmed.

Having thus described the basic concepts, it may be rather apparent tothose skilled in the art after reading this detailed disclosure that theforegoing detailed disclosure is intended to be presented by way ofexample only and is not limiting. Various alterations, improvements, andmodifications may occur and are intended to those skilled in the art,though not expressly stated herein. These alterations, improvements, andmodifications are intended to be suggested by this disclosure, and arewithin the spirit and scope of the exemplary embodiments of thisdisclosure.

Moreover, certain terminology has been used to describe embodiments ofthe present disclosure. For example, the terms “one embodiment,” “anembodiment,” and/or “some embodiments” mean that a particular feature,structure or characteristic described in connection with the embodimentis included in at least one embodiment of the present disclosure.Therefore, it is emphasized and should be appreciated that two or morereferences to “an embodiment” or “one embodiment” or “an alternativeembodiment” in various portions of this specification are notnecessarily all referring to the same embodiment. Furthermore, theparticular features, structures or characteristics may be combined assuitable in one or more embodiments of the present disclosure.

Further, it will be appreciated by one skilled in the art, aspects ofthe present disclosure may be illustrated and described herein in any ofa number of patentable classes or context including any new and usefulprocess, machine, manufacture, or composition of matter, or any new anduseful improvement thereof. Accordingly, aspects of the presentdisclosure may be implemented entirely hardware, entirely software(including firmware, resident software, micro-code, etc.) or combiningsoftware and hardware implementation that may all generally be referredto herein as a “unit,” “module,” or “system.” Furthermore, aspects ofthe present disclosure may take the form of a computer program productembodied in one or more computer readable media having computer readableprogram code embodied thereon.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including electro-magnetic, optical, or thelike, or any suitable combination thereof. A computer readable signalmedium may be any computer readable medium that is not a computerreadable storage medium and that may communicate, propagate, ortransport a program for use by or in connection with an instructionexecution system, apparatus, or device. Program code embodied on acomputer readable signal medium may be transmitted using any appropriatemedium, including wireless, wireline, optical fiber cable, RF, or thelike, or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of thepresent disclosure may be written in any combination of one or moreprogramming languages, including an object-oriented programming languagesuch as Java, Scala, Smalltalk, Eiffel, JADE, Emerald, C++, C#, VB. NET,Python or the like, conventional procedural programming languages, suchas the “C” programming language, Visual Basic, Fortran 2003, Perl, COBOL2002, PHP, ABAP, dynamic programming languages such as Python, Ruby andGroovy, or other programming languages. The program code may executeentirely on the user's computer, partly on the user's computer, as astand-alone software package, partly on the user's computer and partlyon a remote computer or entirely on the remote computer or server. Inthe latter scenario, the remote computer may be connected to the user'scomputer through any type of network, including a local area network(LAN) or a wide area network (WAN), or the connection may be made to anexternal computer (e.g., through the Internet using an Internet ServiceProvider) or in a cloud computing environment or offered as a servicesuch as a Software as a Service (SaaS).

Furthermore, the recited order of processing elements or sequences, orthe use of numbers, letters, or other designations therefore, is notintended to limit the claimed processes and methods to any order exceptas may be specified in the claims. Although the above disclosurediscusses through various examples what is currently considered to be avariety of useful embodiments of the disclosure, it is to be understoodthat such detail is solely for that purpose, and that the appendedclaims are not limited to the disclosed embodiments, but, on thecontrary, are intended to cover modifications and equivalentarrangements that are within the spirit and scope of the disclosedembodiments. For example, although the implementation of variouscomponents described above may be embodied in a hardware device, it mayalso be implemented as a software only solution, e.g., an installationon an existing server or mobile device.

Similarly, it should be appreciated that in the foregoing description ofembodiments of the present disclosure, various features are sometimesgrouped together in a single embodiment, figure, or description thereoffor the purpose of streamlining the disclosure aiding in theunderstanding of one or more of the various embodiments. This method ofdisclosure, however, is not to be interpreted as reflecting an intentionthat the claimed subject matter requires more features than areexpressly recited in each claim. Rather, claimed subject matter may liein less than all features of a single foregoing disclosed embodiment.

1. A method implemented on one or more computing devices for charging anelectric vehicle, each of the one or more computing devices having atleast one processor, at least one storage device and a data exchangeport communicatively connected to a network, the one or more computingdevices including at least one of a first computing device for chargingstation recommendation or a second computing device for chargingcontrol, the method comprising: receiving, by the first computingdevice, a request for charging station recommendation from a clientterminal; determining, by the first computing device, at least onecharging station within a preset distance range of the client terminal;determining, by the first computing device, an evaluation for each ofthe at least one charging station based on one or more evaluationparameters, wherein the one or more evaluation parameters include atleast one of: a price discount provided by the each of the at least onecharging station, a distance between the each of the at least onecharging station and the client terminal, a preset recommendation valuefor the each of the at least one charging station, or a historicalevaluation of the each of the at least one charging station; andtransmitting, by the first computing device, the evaluation of the eachof the at least one charging station and an identifier of the each ofthe at least one charging station to the client terminal.
 2. The methodof claim 1, wherein the determining, by the first computing device, anevaluation for each of the at least one charging station includes:obtaining one or more preset weight values corresponding to the one ormore evaluation parameters, respectively; estimating a weighted sum ofthe one or more evaluation parameters based on the one or more presetweight values; and designating the weighted sum of the one or moreevaluation parameters as the evaluation of the each of the at least onecharging station.
 3. The method of claim 2, wherein the one or morepreset weight values include at least one of: a first preset weightvalue corresponding to the price discount provided by the each of the atleast one charging station being 40%, a second preset weight valuecorresponding to the distance between the each of the at least onecharging station and the client terminal being 35%, a third presetweight value corresponding to the preset recommendation value of theeach of the at least one charging station being 20%, or the fourthpreset weight value corresponding to the historical evaluation value ofthe each of the at least one charging station being 5%.
 4. The method ofclaim 1, further comprising: for each of the at least one chargingstation, determining, by the first computing device, the presetrecommendation value based on one or more recommendation parameters,wherein the one or more recommendation parameters include at least oneof: a number of charging piles at the each of the at least one chargingstation, a real-time parking fee at the each of the at least onecharging station, or a unit charging price associated with the each ofthe at least one charging station.
 5. The method of claim 4, wherein thedetermining the preset recommendation value includes: obtaining one ormore preset percentages corresponding to one of the one or morerecommendation parameters, respectively; and determining the presetrecommendation value based on the one or more preset percentages,wherein the preset recommendation value is equal to a sum of the one ormore recommendation parameters multiplying the corresponding presetpercentage, respectively.
 6. The method of claim 5, wherein the one ormore preset percentages include at least one of: a first presetpercentage corresponding to the number of charging piles at the each ofthe charging station being 45%, a second preset percentage correspondingto the real-time parking fee at the each of the at least one chargingstation being 35%, or a third preset percentage corresponding to thecharging unit price associated with the each of the at least onecharging station being 20%.
 7. The method of any one of claim 1, whereinthe transmitting the evaluation of each of the at least one chargingstation and an identifier of each of the at least one charging stationto the client terminal includes: sorting the at least one chargingstation in a descending order according to the evaluation of the atleast one charging station; and sending the evaluation of each of thesorted at least one charging station and the identifier of each of thesorted at least one charging station to the client terminal for display.8. The method of claim 1, wherein the transmitting the evaluation ofeach of the at least one charging station and an identifier of each ofthe at least one charging station to the client terminal includes:determining whether the evaluation of the each of the at least onecharging station is greater than or equal to a preset threshold; andsending the identifier of the each of the at least one charging stationto the client terminal for display in response to a determination thatthe evaluation is greater than or equal to the preset threshold.
 9. Themethod of claim 1, further comprising: receiving, by the secondcomputing device, a charging request and an associating request forconnecting the client terminal and the second computing device from atarget charging pile at one of the at least one charging station;determining, by the second computing device, charging information forcharging an electric vehicle associated with the client terminal basedon the charging request; establishing, by the second computing device, aconnection between the second computing device and the client terminalbased on the associating request; and sending, by the second computingdevice, the charging information to the target charging pile forcharging the electric vehicle based on the charging information.
 10. Themethod of claim 9, further comprising: obtaining, by the secondcomputing device, a current charging status of the electric vehicle fromthe target charging pile; and sending, by the second computing device,the current charging status to the client terminal through theconnection between the client terminal and the second computing device.11. The method of claim 9, further comprising: determining, by thesecond computing device, whether the charging for the electric vehicleis completed; in response to a determination that the charging for theelectric vehicle is completed, determining, by the second computingdevice, a charging fee corresponding to the charging information;sending, by the second computing device, the charging fee to the clientterminal; and deducting, by the second computing device, the chargingfee from an electronic financial account associated with the clientterminal upon receiving a payment confirmation for the charging fee fromthe client terminal.
 12. A method for charging control of an electricvehicle implemented on a charging management device having at least oneprocessor, at least one storage device and a data exchange portcommunicatively connected to a network, the method comprising:receiving, by the at least one processor, a charging request and anassociating request for connecting a client terminal and the chargingmanagement device from a charging pile; determining, by the at least oneprocessor, charging information for charging an electric vehicleassociated with the client terminal based on the charging request;establishing, by the at least one processor, a connection between thecharging management device and the client terminal based on theassociating request; and sending, by the at least one processor, thecharging information to the charging pile for charging the electricvehicle based on the charging information.
 13. The method of claim 12,further comprising: obtaining, by the at least one processor, a currentcharging status of the electric vehicle from the target charging pile;and sending, by the at least one processor, the current charging statusto the client terminal through the connection between the clientterminal and the charging management device.
 14. The method of claim 12,further comprising: determining, by the at least one processor, whetherthe charging for the electric vehicle is completed; in response to adetermination that the charging for the electric vehicle is completed,determining, by the at least one processor, a charging fee correspondingto the charging information; sending, by the at least one processor, thecharging fee to the client terminal; and deducting, by the at least oneprocessor, the charging fee from an electronic financial accountassociated with the client terminal upon receiving a paymentconfirmation for the charging fee from the client terminal. 15-21.(canceled)
 22. A system for charging an electric vehicle, comprising: atleast one non-transitory storage medium including a set of instructions;and one or more processors in communication with the at least onenon-transitory storage medium, wherein when executing the set ofinstructions, the one or more processors is directed to: receive arequest for charging station recommendation from a client terminal;determine at least one charging station within a preset distance rangeof the client terminal; determine an evaluation for each of the at leastone charging station based on one or more evaluation parameters, whereinthe one or more evaluation parameters include at least one of: a pricediscount provided by the each of the at least one charging station, adistance between the each of the at least one charging station and theclient terminal, a preset recommendation value for the each of the atleast one charging station, or a historical evaluation of the each ofthe at least one charging station; and transmit the evaluation of theeach of the at least one charging station and an identifier of the eachof the at least one charging station to the client terminal. 23-33.(canceled)
 34. The system of claim 22, wherein the determining anevaluation for each of the at least one charging station includes:obtaining one or more preset weight values corresponding to the one ormore evaluation parameters, respectively; estimating a weighted sum ofthe one or more evaluation parameters based on the one or more presetweight values; and designating the weighted sum of the one or moreevaluation parameters as the evaluation of the each of the at least onecharging station.
 35. The system of claim 22, wherein the one or moreprocessors is further directed to: for each of the at least one chargingstation, determine the preset recommendation value based on one or morerecommendation parameters, wherein the one or more recommendationparameters include at least one of: a number of charging piles at theeach of the at least one charging station, a real-time parking fee atthe each of the at least one charging station, or a unit charging priceassociated with the each of the at least one charging station.
 36. Thesystem of claim 22, wherein the transmitting the evaluation of each ofthe at least one charging station and an identifier of each of the atleast one charging station to the client terminal includes: determiningwhether the evaluation of the each of the at least one charging stationis greater than or equal to a preset threshold; and sending theidentifier of the each of the at least one charging station to theclient terminal for display in response to a determination that theevaluation is greater than or equal to the preset threshold.
 37. Thesystem of claim 22, wherein the one or more processors is furtherdirected to: receive a charging request and an associating request forconnecting the client terminal and the second computing device from atarget charging pile at one of the at least one charging station;determine charging information for charging an electric vehicleassociated with the client terminal based on the charging request;establish a connection between the second computing device and theclient terminal based on the associating request; and send the charginginformation to the target charging pile for charging the electricvehicle based on the charging information.
 38. The system of claim 37,wherein the one or more processors is further directed to: determinewhether the charging for the electric vehicle is completed; in responseto a determination that the charging for the electric vehicle iscompleted, determine a charging fee corresponding to the charginginformation; send the charging fee to the client terminal; and deductthe charging fee from an electronic financial account associated withthe client terminal upon receiving a payment confirmation for thecharging fee from the client terminal.